https://bugs.winehq.org/show_bug.cgi?id=48166
Bug ID: 48166
Summary: test.winehq.org Provide a way to track individual
failures
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A test unit may have multiple unrelated test failures. Some may fail on recent
Windows 10 machines while others may only happen in certain locales or some
graphics cards. Untangling these can actually be automated.
The root is to merge the failures of two reports together while associating
each failure with the tag or the report(s) it originates from. To do so diff
the two error lists.
* Failures that are present in both get both tags.
* Failures that are only present in the first report get only that tag.
* Same thing for failures that are present only in the second report.
And all failures are integrated in the merged list in the order they are
returned in by Algorithm::Diff.
Once two failure lists have been merged together, it's possible to continue
merging more failure lists. This allows getting a unified list of the failures
of a given commitid, and appending that commitid to the tags allows building a
complete list of all the available history.
Then one can group all failures that have the exact same set of tag+commitids
combinations together. Then, since the failures in different groups don't all
happen together they must depend on different factors.
Intermittent failures, timeouts, crashes
----------------------------------------
If two failures are related but a random timeout or crash sometimes occurs
between them they might end up being incorrectly split in two separate groups.
So if a crash or a timeout occurs, any other failure in that run should be
ignored when grouping failures together.
This can be achieved by prefixing the tag with a '*' if a crash or timeout
occured. Then, when grouping failures together, ignore the entries where the
tag starts with a '*'. But when building the occurence pattern, do use the
entries starting with a '*' to show all the test runs where at least one of the
failures in the group occurred.
Because entries starting with a '*' are ignored when building failure groups,
failures that cause a crash/timeout and the crash/timeout line itself will be
part of no failure group. So do a second pass over the unassigned failures,
this time not ignoring the entries with a '*'. This will create groups composed
of the crash/timeout and any related failures.
New failures
------------
This analysis indicates where and when a given failure group happened. This
means it can also detect new failures.
It would not be useful to define a new failure as one that never happened
before the latest commit: blink and you might miss it. Instead it should be
expanded to all failures that only happened in the first half of the available
history. This may sometimes falsely treat rare intermittent failures as new but
that should be rare enough.
Presentation of the results
---------------------------
The results can be presented on a page with one box per test unit like the
'Full Report' pages. A 'details' link under the test unit name on the test
failrues pattern page would link to the relevant section of the full page.
Inside each box there would be a sequence of lines showing the failures in a
group, followed by the usual pattern showing which machines the failure happens
on; then the next failure group, etc. For instance:
console.c:270: Test failed: got 16, expected 6
console.c:275: Test failed: got 16, expected 6
.....F..F...F..F.mmm Win8 vm1
......FF.e...FF.e..F Win8 vm1-ja
096c:console: unhandled exception c0000005 at 6F384E33
.....CC Win8 vm2-new
As usual the items in the pattern would link to the relevant pages, allowing to
dig deeper into the issue. The same color coding would be used for the pattern
but since failure groups always have the same number of failures only one color
would be used for the F code.
The failure line number will change from one run to the next so zero it out or
only retain one value at random. Similarly, if the failure contains timing
information (see bug 48094), remove the timing information.
If a failure is identified as new, put its lines in bold orange, like on the
TestBot. This will allow quick identification of the new failures on the page.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48177
Bug ID: 48177
Summary: Microsoft SQL Server Management Studio 18.4 installer
silently exits
Product: Wine
Version: 4.20
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: damjan.jov(a)gmail.com
Distribution: ---
$ wine SSMS-Setup-ENU.exe
0009:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0009:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ...,
TokenElevation, ...) semi-stub
(exits immediately, no UI)
$ md5sum SSMS-Setup-ENU.exe
65d034096b63c6ec9051951bcf10088c SSMS-Setup-ENU.exe
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48151
Bug ID: 48151
Summary: AceMoney (or any other non-unicode program): can't
enter cyrillic letters into text fields when using
custom keyboard layout
Product: Wine
Version: 4.20
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ttyusupov(a)gmail.com
macOS version: 10.14.6 (18G1012)
Link to a free version of the app:
http://cdn.mechcad.net/downloads/AceMoneyLiteSetup.exe
How to reproduce:
1) Install custom keyboard layout with Cyrillic support, for example:
https://github.com/asizikov/osx-russian-keyboard
2) Setup AceMoneyLite under Wine. Actually you don't need even complete setup -
you can just run the installer and try to type Cyrillic letter using custom
keyboard layout into a text field where it asks for the path to install.
Expected result:
- Cyrillic letters entered and shown correctly.
Actual result:
- Cyrillic letters are entered and displayed as question marks '?'.
Note: I've used LANG, LC_ALL and other variables with different values
including ru_RU.UTF-8 - this help with showing text labels, but doesn't affect
entering Cyrillic letters into text field for non-unicode apps.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=18985
Summary: Two bugs in HTML-kit
Product: Wine
Version: 1.1.23
Platform: PC
URL: http://htmlkit.com/download/
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
Hi, a user reported trouble with this app here:
http://ubuntuforums.org/showthread.php?t=1190483
I gave it a try and actually there seem to be two bugs:
1. All icons in toolbar are black. In the console the line appears:
err:imagelist:IMAGELIST_InternalExpandBitmaps creating new image bitmap
(x=25600 y=16)!
2. After doing from the menu: Edit->Prefernces->OK an access violation occurs
and the app is no longer usable.
Both bugs are gone using native comctl32
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47706
Bug ID: 47706
Summary: ntdll: Compiler warnings regression on x86_64 [stable]
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: kakurasan(a)gmail.com
Regression SHA1: 95f94568158caaf4fefe2e14f21bb3f0701577c9
Distribution: ---
Created attachment 65177
--> https://bugs.winehq.org/attachment.cgi?id=65177
Warning messages
I'll submit a patch to wine-devel.
--- Architecture ---
x86_64, Win64 build
--- Compiler ---
gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0
--- Result of "git bisect" ---
95f94568158caaf4fefe2e14f21bb3f0701577c9 is the first bad commit
commit 95f94568158caaf4fefe2e14f21bb3f0701577c9
Author: Vijay Kiran Kamuju <infyquest(a)gmail.com>
Date: Tue Apr 16 11:27:16 2019 +0200
ntdll: Report system information SystemPerformanceInformation info class.
Based on patch from Michael Müller.
Signed-off-by: Vijay Kiran Kamuju <infyquest(a)gmail.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
(cherry picked from commit 99ba65a1ea2c1546a61c3ed40996cbfee9d25f69)
Signed-off-by: Michael Stefaniuc <mstefani(a)winehq.org>
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=12332
Summary: driver dev kit won't install
Product: Wine
Version: 0.9.58.
Platform: PC-x86-64
URL: http://download.microsoft.com/download/9/0/f/90f019ac-
8243-48d3-91cf-81fc4093ecfd/1830_usa_ddk.iso
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: setupapi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: htl10(a)users.sourceforge.net
This seems to be a problem with setupapi rather than msi... in an case, I am
just after the documentations and the examples, so I just like it to unpack
nicely, the result doesn't need to be functional...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47578
Bug ID: 47578
Summary: Omni-NFS 4.13's XLPD Server crashes on unimplemented
function ntoskrnl.exe.MmIsThisAnNtAsSystem
Product: Wine
Version: 4.12.1
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 64983
--> https://bugs.winehq.org/attachment.cgi?id=64983
console output
Steps to reproduce:
1. Create and use a 32-bit Wine prefix. Omni-NFS 4.13 is not compatible with
64-bit Windows.
2. Download and install Omni-NFS 4.13 (liteall.exe) from
https://download.cnet.com/Omni-NFS/3000-2085_4-10052498.html
3. Start the XLPD Server from the start menu or by running `wine 'C:\Program
Files\NFSLite\xlpd.exe'`
Console output is attached.
$ sha256sum liteall.exe
52b4f4a7ec71389b8344521393eb8abd6c7c0e7a52be147ece033790ae5cb8ce
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42374
Bug ID: 42374
Summary: Hardwood Solitaire
Product: Wine
Version: 2.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 57157
--> https://bugs.winehq.org/attachment.cgi?id=57157
Hardwood Solitaire wine log
Hello,
Hardwood Solitaire can not connect to his server. So you can not use the
network features:
- play paid games
- no access to achievements
- store empty, no objects
...
How to reproduce:
1) download Hardwood solitaire here:
http://www.silvercrk.com/solitaire/
and install it with Wine.
2) launch it, click on "Store", the Store is empty, you can not access
anything.
3) you can sign in too and when you are connected to your account, you have an
error message:
"Couldn't connect to server. Full access to game feature may not be available
at this time."
I joined the Wine log, it could be related to this lines:
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 60000
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 60000
fixme:wininet:InternetSetOptionW INTERNET_OPTION_HTTP_DECODING; STUB
fixme:msvcrt:__clean_type_info_names_internal (0x3d75bc) stub
fixme:msvcrt:__clean_type_info_names_internal (0x154541c) stub
fixme:msvcrt:__clean_type_info_names_internal (0xaa423c) stub
fixme:msvcrt:__clean_type_info_names_internal (0x39037c) stub
Thank you for your help.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45757
Bug ID: 45757
Summary: Visual Studio 2017 Installer - "The installer manifest
failed signature validation"
Product: Wine
Version: 3.15
Hardware: x86
URL: https://visualstudio.microsoft.com/downloads/#build-to
ols-for-visual-studio-2017
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Depends on: 45749
Distribution: ---
Follow up to bug 45749.
After the workaround, the installer opens. But installing anything errors
instantly with "The installer manifest failed signature validation"
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47418
Bug ID: 47418
Summary: Quickbooks 2018 installer crashes on Validating
Install.
Product: Wine
Version: 4.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yother.andrew(a)gmail.com
Distribution: ---
Created attachment 64764
--> https://bugs.winehq.org/attachment.cgi?id=64764
msiexec backtrace
Zorin OS 15 Core using Linux Kernel 4.18 x86-64
Wine 4.11 x86 wineprefix with dotnet472 vcrun2008-2017 and corefonts
The QuickBooks 2018 Premier installer crashes during the validating install
stage with a msiexec crash screen.
Unfortunately I cannot provide a setup file due to licensing.
Backtrace and full terminal output are attached.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.