Status: Started Owner: kuch...@chromium.org CC: a...@chromium.org Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 7428 by kuch...@chromium.org: Wrong tests being marked as timed out from TestShell http://code.google.com/p/chromium/issues/detail?id=7428 Mads noticed this problem and said this in an email: It seems that if a test that uses waitUntilDone fails to call notifyDone, the *next* test that is run will time out. I think this is the reason for the new failures you got after this change to dump on notifyDone. I guess nothing is dumped if you fail to call notifyDone? To reproduce, here is an example: [a...@ager-xp:/cygdrive/c/chrome/src/webkit/tools/layout_tests]$ ./run_webkit_tests.sh LayoutTests/fast/dom/Window/clear-timeout.html LayoutTests/fast/dom/Window/window-property-shadowing.html This will have window-property-shadowing pass. However, if you change clear-timeout.html by deleting the lines that calls notifyDone, then window-property-shadowing will timeout. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
