[Bug 28363] New: test mstask/task_trigger.ok slightly flaky?
http://bugs.winehq.org/show_bug.cgi?id=28363 Summary: test mstask/task_trigger.ok slightly flaky? Product: Wine Version: 1.3.28 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: mstask AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This just happened for me once after about a thousand or so runs: ../../../tools/runtest -q -P wine -M mstask.dll -T ../../.. -p mstask_test.exe.so task_trigger.c && touch task_trigger.ok task_trigger.c:105: Test failed: wStartMinute: Found 46 but expected 47 For what it's worth, this was with WINEDEBUG=warn+heap, and the system was os: Ubuntu 10.04.3 LTS, 2.6.32-33-generic, pulseaudio 0.9.21-63-gd3efa-dirty, Advanced Linux Sound Architecture Driver Version 1.0.21. ram: 3212 MB cpu: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz gpu: GeForce GT 240/PCI/SSE2 3.2.0 NVIDIA 195.36.24 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=28363 --- Comment #1 from Dan Kegel <dank(a)kegel.com> 2011-09-13 10:25:15 CDT --- http://test.winehq.org/data/tests/mstask:task_trigger.html shows no failures in several dozen runs (not especially surprising, given how seldom it fails here). Oddly, I can't browse to that info, I had to google it. mstask doesn't seem to show up in the summaries on test.winehq.org. -- 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=28363 --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- Is this still an issue in current (1.7.36 or newer) wine? -- 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=28363 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fgouget(a)codeweavers.com Keywords| |source, testcase -- 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=28363 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|test mstask/task_trigger.ok |mstask:task_trigger - |slightly flaky? |test_SetTrigger_GetTrigger( | |) slightly flaky? Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #3 from François Gouget <fgouget(a)codeweavers.com> --- Unfortunately this report does not indicate which of the test_SetTrigger_GetTrigger() tests failed (that's very much a compare_trigger_state() bug, will send patches). And since there is no record of this failure in the available WineTest results I think we should close this bug.
Oddly, I can't browse to that info, I had to google it. mstask doesn't seem to show up in the summaries on test.winehq.org.
The summaries only show failing tests. Otherwise they would be lost in a sea of successful tests (although maybe not so much these days). The way to get to the tests that never fails is to open the test info from the column header and then switch to the full report. -- 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=28363 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla