http://bugs.winehq.org/show_bug.cgi?id=28503
Summary: comctl32/treeview.ok fails occasionally Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
This failed just now on Austin's buildslave with WINEDEBUG=warn+heap:
../../../tools/runtest -q -P wine -M comctl32.dll -T ../../.. -p comctl32_test.exe.so treeview.c && touch treeview.ok treeview.c:1512: Test failed: got 0x20318a treeview.c:1518: Test failed: got 0x20318a
and again on his buildslave without WINEDEBUG:
treeview.c:1512: Test failed: got 0x201c8b treeview.c:1518: Test failed: got 0x201c8b
I see it's happened at least once before, last month, to someone else:
http://test.winehq.org/data/6ee95c77381791299ae040248897ac58c74f49f6/linux_o...
and I think I recall seeing it one other time on the buildbot (not sure which slave).
Austin's buildslave's info:
os: Debian GNU/Linux testing (wheezy), 3.0.0-1-686-pae, , Advanced Linux Sound Architecture Driver Version 1.0.24. ram: 8113 MB cpu: AMD Phenom(tm) II X4 940 Processor gpu: GeForce 9800 GTX+/PCI/SSE2/3DNOW! 3.3.0 NVIDIA 285.03
It's possible this is caused by someone playing with the mouse or keyboard while the tests are running, but seeing it twice in a row is suspicious.
http://bugs.winehq.org/show_bug.cgi?id=28503
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com Version|unspecified |1.3.29
--- Comment #1 from Austin English austinenglish@gmail.com 2011-09-25 23:23:38 CDT --- No, the keyboard/mouse weren't touched during the test runs.
http://bugs.winehq.org/show_bug.cgi?id=28503
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com 2011-09-26 01:17:14 CDT --- (In reply to comment #1)
No, the keyboard/mouse weren't touched during the test runs.
Yeah, it's not about events it seems. I see it sometimes too, GetPixel() fails to return expected color, maybe it's a race in message processing of some kind or GetPixel() is not reliable enough in x11drv, I'm not sure.
http://bugs.winehq.org/show_bug.cgi?id=28503
--- Comment #3 from Dan Kegel dank@kegel.com 2011-09-26 08:54:01 CDT --- I'm seeing a whole lot of
olepicture.c:696: Test failed: Color at 5,5 should have changed, but still was 0x380D35 make: *** [olepicture.ok] Error 1
on that same buildslave of Austin's, perhaps it's the same bug.
http://bugs.winehq.org/show_bug.cgi?id=28503
--- Comment #4 from Dan Kegel dank@kegel.com 2011-10-20 06:43:24 CDT --- *** Bug 28819 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=28503
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #5 from Austin English austinenglish@gmail.com --- test.winehq.org is clean for this test over the past month, and I just ran it in a loop with/without warn+heap for 1000 times, no failures.
https://bugs.winehq.org/show_bug.cgi?id=28503
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.37.
https://bugs.winehq.org/show_bug.cgi?id=28503
Saulius K. saulius2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2@gmail.com
-
wine-bugs＠winehq.org