http://bugs.winehq.org/show_bug.cgi?id=17063
Summary: Test results page should distinguish between 32-bit and 64-bit Product: WineHQ.org Version: unspecified Platform: All URL: http://test.winehq.org/data OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: www-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com
Looking at http://test.winehq.org/data, it's hard to find x86-64 test results (wine or windows). We should probably separate them out into their own column next to the 32-bit OS, e.g.:
Win2k3 WinXP-32bit WinXP-64bit ... Wine-32bit Wine-64bit
We've got Platform under the report info that shows if it's x86 or x86_64, so extending tools/winetest/dissect to account for this shouldn't be too much trouble for a perl guru.
http://bugs.winehq.org/show_bug.cgi?id=17063
--- Comment #1 from Alexandre Julliard julliard@winehq.org 2009-01-21 16:51:20 --- It's easy to do, but I'm not convinced it's a good idea. It's quite useful to be able to see the 32-bit and 64-bit results side by side for the same version.
http://bugs.winehq.org/show_bug.cgi?id=17063
--- Comment #2 from Austin English austinenglish@gmail.com 2009-01-21 18:54:07 --- (In reply to comment #1)
It's easy to do, but I'm not convinced it's a good idea. It's quite useful to be able to see the 32-bit and 64-bit results side by side for the same version.
I can see that. I was browsing the results and couldn't find an easy way to identify where there were 64-bit results. E.g., just by looking at the top, there's no way to know if there are any 64-bit results...you have to click the XP/Vista/Wine link before you can see them.
http://bugs.winehq.org/show_bug.cgi?id=17063
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #3 from André H. nerv@dawncrow.de 2011-07-20 15:58:18 CDT --- so it shouldn't be split up, but having a visible sign that this is 32-bit and this 64-bit would be great...
http://bugs.winehq.org/show_bug.cgi?id=17063
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other OS/Version|All |other
--- Comment #4 from Austin English austinenglish@gmail.com 2012-02-23 15:19:50 CST --- Removing deprecated 'All' Platform/OS.
http://bugs.winehq.org/show_bug.cgi?id=17063
Helen Hernandez lilhomiefoo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lilhomiefoo@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=17063
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fgouget@codeweavers.com
--- Comment #5 from François Gouget fgouget@codeweavers.com --- The tags usually come to the rescue: * The TestBot VMs are all 32 bit unless the tag has a '-64' suffix. * My Windows VMs are all 32 bit unless they have a 't64' suffix. * My Linux boxes have a '-t32', '-wow32' or '-wow64' suffix, which corresponds to 32 bit tests, 32 bit tests in a 32/64 bit capable wineprefix, and 64 bit tests in a 32/64 bit capable suffix respectively. * Other Wine boxes are all 32 bit.
That said, instead of repeating the platform name in each column (e.g. 'Win7'), one could put the bitness of the tests.
https://bugs.winehq.org/show_bug.cgi?id=17063
--- Comment #6 from François Gouget fgouget@codeweavers.com --- Another approach has been taken: printing the pid on the test summary lines. See the commits below.
The TestBot has support for using the pids and test.winehq will too soon. What remains to be done is either updating TestLauncher.exe (used by the TestBot) or replacing it with WineTest.exe somehow.
commit 873eace6e496a154f333426aeb2b3e0ad79ba44d Author: Francois Gouget fgouget@codeweavers.com Date: Wed Feb 22 15:33:21 2017 +0100
wine/test.h: Identify the process responsible for test summary lines.
Currently the child process summary lines are indistinguishable from the main process one. This makes it impossible to automatically detect when a process exits abruptly, i.e. without printing a summary line, if it has run a subprocess.
This will let analysis tools identify which summary lines correspond to processes they started and thus when some are missing. Note also that in case of a crash the 'unhandled exception' play the same role as the test summary lines. Thus it is important to also tag them with the pid of the source process.
Signed-off-by: Francois Gouget fgouget@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
commit 873eace6e496a154f333426aeb2b3e0ad79ba44d Author: Francois Gouget fgouget@codeweavers.com Date: Wed Feb 22 15:33:21 2017 +0100
wine/test.h: Identify the process responsible for test summary lines.
Currently the child process summary lines are indistinguishable from the main process one. This makes it impossible to automatically detect when a process exits abruptly, i.e. without printing a summary line, if it has run a subprocess.
This will let analysis tools identify which summary lines correspond to processes they started and thus when some are missing. Note also that in case of a crash the 'unhandled exception' play the same role as the test summary lines. Thus it is important to also tag them with the pid of the source process.
Signed-off-by: Francois Gouget fgouget@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
-
wine-bugs＠winehq.org