wine-bugs October 2020

wine-bugs@winehq.org

1 participants
6894 discussions

[Bug 48164] New: test.winehq.org should provide an efficient way to detect new failures
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48164 Bug ID: 48164 Summary: test.winehq.org should provide an efficient way to detect new 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: --- Problem ------- test.winehq.org does not allow performing the following tasks efficiently: 1. Detecting when a new failure slips past the TestBot. One can detect new failures on the per test unit page when specific columns turn red. But quite often the test unit already has failures so one has to look at the specific number of failures. Furthermore many test units currently have failures so this requires checking 80+ pages individually. 2. Detecting when the results on a VM degrade. After upgrading a machine it's useful to compare it to its previous results. But the results for each date are on separate pages. So again it's necessary to check the per-test-unit result pages. 3. Comparing the results of two machines of different platforms. For instance comparing the results of running Windows 8 to those of Windows 10 on the same hardware. Other things that got asked: 4. Sometimes it would be nice to have only the failures, and not all the lines with skipped tests and todos. 5. In some cases it would also be nice to have pages with only the failures that happen on TesBot VMs since these are usually easier to reproduce. Jeremy's page ------------- Jeremy's test summary page can help with some of that: https://www.winehq.org/~jwhite/latest.html But: * It's not integrated with test.winehq.org which makes it hard to find. * There are only two states: Success and Failed: So it does not help when a test goes from having 2 failures to 4, or when it has a set of systematic failures and a set of intermittent ones. * The failed / success pattern is not per VM which masks some patterns and does not help with point 2. Proposal -------- A modified version of Jeremy's page could be integrated with test.wnehq.org: * It would actually be a pair of 'Failures' pages, one for TestBot VMs and one for all test results. Both would be linked to from the top of the main index page, for instance using the same type of 'prev | next' text links used on the other pages. * Jeremy's result matrix would be extended from three to four dimensions; test units, test results, time, and number/type of failures. * As before the results would be grouped per test unit in alphabetical order. Only the test units having at least one error, recent or not, would be shown. This could again be in the form of an array ('full report' pages on test.winehq.org) or simply test unit titles (TestBot jobDetails page style) with the information about each test unit inside. Clicking on the test unit name would link to its 'test runs' page on test.winehq.org. * For each test unit there would be one line per test result having errors. The first part of the line would have one character per commit for the whole history available on test.winehq.org. That character would indicate if the test failed and more. The second part of the line would be the test result platform and tag. They would be sorted per platform and alphabetically. * Each test result would get a one character code: . Success F Failure C Crash T Timeout m Missing dll (foo=missing or other error code) e Other dll error (foo=load error 1359 and equivalent) _ No test (the test did not exist) ' ' No result (the machine did not run the tests that day) * These codes would be shown using a monospace font so they would form a pattern across time and test results: .....F..F...F..F.mmm Win8 vm1 .....FFFFeFFFFFFeFFF Win8 vm1-ja ...TTCC Win8 vm2-new ......eF...F...F..F. Win10 vm3 * Each character would have a tooltip containing details like the meaning of the letter, the number of failures, or the dll error message. They would also link to the corresponding section of the test report. * In addition to the character the background would be color coded to make patterns more visible. . Green F Green to yellow to red gradient C Dark red T Purple/pink m Cyan e Dark blue _ Light gray ' ' White * The green-yellow-red gradient would be what allows detecting changes in the number of test failures. That gradient must be consistent for all lines of a given test unit's pattern. Furthermore the gradient must not be computed based on the test result's number of failures. That is, if a test unit has either 100 or 101 failures, those must not have nearly indistinguishable colors. Instead the set of all different failure counts for the test unit should be collected. Zero should be added to that set. Then these values should be sorted and a color attributed for each *index*. Then the background color is selected based on the index of that result's failures count. It is expected that each set will be relatively small so that the colors will be reasonably far apart, making it easy to distinguish a shift from 4 to 6 failures even if there are 100 failures from time to time. Also note hat adding zero to the set essentially reserves green for successful results. Implementation feasibility -------------------------- * No changes in dissect. * In gather, generate a new testunits.txt file containing one line per test unit: - The data source would be the per-report summary.txt files. -> These don't indicate when a timeout has occurred so timeouts will appear as F instead which is acceptable for a first implementation. - The first line would contain a star followed by the tags of all the test runs used to build the file: - The other lines would contain the name of the test unit followed by space-separated pairs of result code/failure count and result tag (including the platform). - A line would be put out even if the test unit had no failure. For instance, the commit1 testunit.txt file could contain: * win8_vm1 win8_vm1-ja win8_vm2-new win10_vm3 foo:bar 43 win8_vm1-ja C win8_vm2-new e win10_vm3 foo:bar2 - In the example above win8_vm1 only appears on the first line. This means WineTest was run on that machine but had no failure at all. - If the results for commit2 refer to a win8_vm4 machine, we will know that the reason win8_vm4 does not appear in commit1 file is not because all the tests succeeded, but because WineTest was not run on win8_vm4 for commit1. This means that the result code for win8_vm4 for commit1 should be ' '. not '.' for all test units. - If commit2 has results for the foo:bar3 test unit, then we will know the reason it is not present in the commit1 file is not because all the test runs were successful, but because foo:bar3 did not exist yet. So its result code would be '_', not '.'. * Add a new build-failures script to generate both failures pages. - This script will need to read the testunits.txt file for all the commits. The simplest implementation will be to read all the data into memory before generating the page. This will avoid having to deal with keeping the current test unit synchronized between all of the testunits.txt files when a new test unit has been added. - The combined size of the testunits.txt files is expected to be reasonable, within a factor of 3 of the summary.txt files. For reference, here is some data about the sizes involved: $ du -sh data 21G data $ ls data/*/*/report | wc -l 2299 $ cat data/*/*/report | wc 34,087,987 231,694,407 2,104,860,095 $ cat data/*/*/report | egrep '(: Test failed:|: Test succeeded inside todo block:|done [(]258)|Unhandled exception:)' | wc 567,158 6,275,504 53,202,999 $ cat data/*/summary.txt | wc 186,219 3,046,363 30,596,901 - Having a function to generate the page will allow calling it twice in a row to generate both pages without having to load and parse the testunits.txt files twice. -- 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.

1 5

[Bug 49058] New: https://source.winehq.org/git/website.git/ directs users to clone from http://, not https://
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=49058 Bug ID: 49058 Summary: https://source.winehq.org/git/website.git/ directs users to clone from http://, not https:// 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: austinenglish(a)gmail.com Distribution: --- austin@laptop /tmp $ git clone http://source.winehq.org/git/wine.git Cloning into 'wine'... warning: redirecting to https://source.winehq.org/git/wine.git/ Looks like this is in the website config: https://source.winehq.org/git/website.git/blob/dccd8b12e3bce9d7a9cc2112e511… note, applies to the other git repos as well. -- 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.

1 4

[Bug 42309] New: The Crew (Uplay) crashes at start
by wine-bugs＠winehq.org 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=42309 Bug ID: 42309 Summary: The Crew (Uplay) crashes at start Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 57043 --> https://bugs.winehq.org/attachment.cgi?id=57043 Unhandled page fault read access to 0x0 in 64-bit code backtrace After the loading screen has closed, the screen goes black and then wine crashes with a read access to 0x00000000 in 64-bit code. The terminal is also filled with DirectX 11 fixme's. Tested on wine 2.0 + staged patch from bug 41356. -- 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.

2 21

[Bug 45103] New: FlixGrab: Crashes on launch after showing the splash screen
by wine-bugs＠winehq.org 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=45103 Bug ID: 45103 Summary: FlixGrab: Crashes on launch after showing the splash screen Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lucas.halbig(a)gmail.com Distribution: --- Created attachment 61276 --> https://bugs.winehq.org/attachment.cgi?id=61276 backtrace file when app crashed When attempting to launch https://www.freegrabapp.com/flixgrab after installation it failes to go past the splash screen. -- 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.

2 8

[Bug 48758] New: ConEmu Ctrl+c has different behavior
by WineHQ Bugzilla 30 Mar '22

30 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=48758 Bug ID: 48758 Summary: ConEmu Ctrl+c has different behavior Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- In ConEmu, Ctrl+c behavior is different on Wine and Windows. ConEmu+Cmd on Windows: Ctrl+c breaks current command and starts new empty prompt Ctrl+C shows ^C ConEmu+Cmd on Wine: Ctrl+c shows 'c' Ctrl+C terminates ConEmu completely ConEmu+Far Manager+console application on Windows: Ctrl+c terminates the application Ctrl+C shows ^C ConEmu+Far Manager+console application on Wine: Ctrl+c does nothing or shows 'c' Ctrl+C terminates the application -- 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.

1 17

[Bug 21936] New: rtld mmap failed mapping on OpenBSD
by wine-bugs＠winehq.org 27 Mar '22

27 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=21936 Summary: rtld mmap failed mapping on OpenBSD Product: Wine Version: 1.1.40 Platform: x86 URL: http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/ wine/patches/patch-libs_wine_mmap.c?rev=1.1;content-ty pe=text%2Fplain OS/Version: OpenBSD Status: NEW Keywords: download, patch, source Severity: blocker Priority: P2 Component: loader AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com /home/austin/wine-git/loader/wine: rtld mmap failed mapping /home/austin/wine-git/dlls/ntdll/ntdll.dll.so. wine: failed to initialize: File not found Patch in url fixes the loader on OpenBSD. Need to test on other OS's before submitting to wine-patches. Review of the patch in the meantime is appreciated. -- 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.

2 25

[Bug 29354] New: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog
by wine-bugs＠winehq.org 27 Mar '22

27 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=29354 Bug #: 29354 Summary: Microsoft Virtual PC 2007 SP1 installer fails to get past the "Product Key" dialog Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, split off bug mentioned in http://bugs.winehq.org/show_bug.cgi?id=17512#c3 to track what is most likely a regression ... --- quote --- Tested in 1.3.19 Didn't crash but I couldn't get past the "Product Key" screen. The "Next" button didn't seem to do anything. --- quote --- The problem in Microsoft Virtual PC 2007 SP1 installer is the "ValidateProductID" standard action. Dump using ORCA: --- snip --- CustomerInformationDialog NextButton NewDialog ReadyToInstallDialog PIDRET = 0 4 CustomerInformationDialog NextButton DoAction CA_ValidatePID NOT ProductID AND PIDKEY AND PIDKEY<>" " 1 CustomerInformationDialog NextButton DoAction CA_InstallForAllUsers NOT VPC2004INSTALLED 2 CustomerInformationDialog NextButton DoAction CA_SetTargetPathOnUpgrade VPC2004INSTALLED 3 --- snip --- First condition, if true -> CA_ValidatePID gets executed. --- snip --- 0023:trace:msi:MSI_EvaluateConditionW L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"ProductID" ... 0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for property L"PIDKEY" ... 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"NOT ProductID AND PIDKEY AND PIDKEY<>\" \"" --- snip --- (not fulfilled) Another condition to reach "ReadyToInstallDialog" is "PIDRET = 0". --- snip --- 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action start 18:26:06: ValidateProductID." 0023:trace:msi:msi_get_property returning L"74216<````=````=````=````=`````>@@@@@" for property L"PIDTemplate" 0023:fixme:msi:ACTION_ValidateProductID partial stub: template L"74216<````=````=````=````=`````>@@@@@" key L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:msi_set_property 0x13ce60 L"ProductID" L"PWCVDGDPM7P23VYG6QM4R8Y8T" 0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action ended 18:26:06: ValidateProductID. Return value 0." ... 0023:trace:msi:MSI_EvaluateConditionW L"PIDRET = 0" 0023:trace:msi:msi_get_property property L"PIDRET" not found 0023:trace:msi:MSI_EvaluateConditionW 0 <- L"PIDRET = 0" --- snip --- The "PIDRET" property never exists hence the installation is stuck in "CustomerInformationDialog". If you google for "Adding PIDRET property" you will find many similar looking msi logs, suggesting that this property is added during ValidatePID custom action: --- snip --- MSI (c) (DC:20) [17:55:05:750]: Doing action: ValidatePID MSI (c) (DC:20) [17:55:05:750]: Note: 1: 2205 2: 3: ActionText Action 17:55:05: ValidatePID. Action start 17:55:05: ValidatePID. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PID property. Its value is '58730-000-0000007-05734'. MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding ProductID property. Its value is '58730-000-0000007-05734'. ... MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PIDRET property. Its value is '0'. Action ended 17:55:05: ValidatePID. Return value 1. --- snip --- Because ProductID was set earlier during ValidateProductID standard action, CA_ValidatePID is never executed. http://source.winehq.org/git/wine.git/blob/8cc5561fbf9f3250fbd2d986390e4013… If you remove line 6891 the installer executes the custom action which allows to proceed and let the installation finally succeed. You need 'winetricks mfc42' for CA_ValidatePID. Regards -- 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.

2 21

[Bug 16221] New: Nota Bene requires AUTOEXEC.NT
by wine-bugs＠winehq.org 26 Mar '22

26 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=16221 Summary: Nota Bene requires AUTOEXEC.NT Product: Wine Version: 1.1.9 Platform: PC URL: https://www.notabene.com/download/demos/nbdemo80.exe OS/Version: Linux Status: NEW Keywords: download, Installer Severity: minor Priority: P2 Component: dos AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Nota Bene, on install, checks for AUTOEXEC.NT in system32. If it doesn't find it, it restores its own copy, but we should have our own copy. Shouldn't take much to implement. -- 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.

2 16

[Bug 46648] New: Core Temp Error
by wine-bugs＠winehq.org 25 Mar '22

25 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=46648 Bug ID: 46648 Summary: Core Temp Error Product: Wine Version: 4.1 Hardware: x86-64 URL: https://www.alcpu.com/CoreTemp/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luca.finizio.mgbx(a)hotmail.it Distribution: Mint Created attachment 63570 --> https://bugs.winehq.org/attachment.cgi?id=63570 console output I downloaded and installed Core Temp from https://www.alcpu.com/CoreTemp/ but I get an Error window when trying to launch it. The error window says "Core Temp did not find any supported processors. This program will not continue." I attach my console output. -- 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.

2 6

[Bug 16222] New: Nota Bene requires CONFIG.NT
by wine-bugs＠winehq.org 25 Mar '22

25 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=16222 Summary: Nota Bene requires CONFIG.NT Product: Wine Version: 1.1.9 Platform: PC URL: https://www.notabene.com/download/demos/nbdemo80.exe OS/Version: Linux Status: NEW Keywords: download, Installer Severity: minor Priority: P2 Component: dos AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Nota Bene, on install, checks for CONFIG.NT in system32. If it doesn't find it, it restores its own copy, but we should have our own copy. Shouldn't take much to implement. -- 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.

2 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs October 2020