Bug 36585 - fast/workers/termination-with-port-messages.html failed on Leopard Release Bot
Summary: fast/workers/termination-with-port-messages.html failed on Leopard Release Bot
Status: RESOLVED DUPLICATE of bug 36646
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-25 01:40 PDT by Eric Seidel (no email)
Modified: 2010-03-31 22:50 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2010-03-25 01:40:10 PDT
fast/workers/termination-with-port-messages.html failed on Leopard Release Bot

http://build.webkit.org/results/Leopard%20Intel%20Release%20(Tests)/r56503%20(12057)/fast/workers/termination-with-port-messages-diffs.txt
--- /Volumes/Big/WebKit-BuildSlave/leopard-intel-release-tests/build/layout-test-results/fast/workers/termination-with-port-messages-expected.txt	2010-03-25 01:24:56.000000000 -0700
+++ /Volumes/Big/WebKit-BuildSlave/leopard-intel-release-tests/build/layout-test-results/fast/workers/termination-with-port-messages-actual.txt	2010-03-25 01:24:56.000000000 -0700
@@ -1 +1,2 @@
+CONSOLE MESSAGE: line 3: JavaScript execution exceeded timeout.
 This test terminates a worker when there are many undelivered MessagePort messages still waiting to be dispatched into the Worker Context. This causes termination of JS execution and test should not try to dispatch the remaining messages. Test succeeds if it does not hang or crash (if worker thread is running in the separate process, that process could hang or crash).

This is the first time I've noticed this test fail on the bot.   I can only assume it's flaky since the checkin which kicked off this build had nothing to do with this test.

The test has only been around for 7 days:
http://trac.webkit.org/browser/trunk/LayoutTests/fast/workers/termination-with-port-messages.html
Comment 2 Eric Seidel (no email) 2010-03-29 11:15:19 PDT
The commit-bot just saw this too:
https://bugs.webkit.org/show_bug.cgi?id=36735#c3
Comment 4 Eric Seidel (no email) 2010-03-31 22:49:59 PDT
Just failed on Snow Leopard as well:
http://build.webkit.org/results/SnowLeopard%20Intel%20Leaks/r56889%20(5473)/fast/workers/termination-with-port-messages-diffs.txt
--- /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-leaks/build/layout-test-results/fast/workers/termination-with-port-messages-expected.txt	2010-03-31 20:40:05.000000000 -0700
+++ /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-leaks/build/layout-test-results/fast/workers/termination-with-port-messages-actual.txt	2010-03-31 20:40:05.000000000 -0700
@@ -1 +1,4 @@
+CONSOLE MESSAGE: line 3: JavaScript execution exceeded timeout.
+CONSOLE MESSAGE: line 3: JavaScript execution exceeded timeout.
+CONSOLE MESSAGE: line 3: JavaScript execution exceeded timeout.
 This test terminates a worker when there are many undelivered MessagePort messages still waiting to be dispatched into the Worker Context. This causes termination of JS execution and test should not try to dispatch the remaining messages. Test succeeds if it does not hang or crash (if worker thread is running in the separate process, that process could hang or crash).
Comment 5 Eric Seidel (no email) 2010-03-31 22:50:42 PDT
I expect this is a dupe of bug 36646.

*** This bug has been marked as a duplicate of bug 36646 ***