Bug 121509 - [Windows] Test Failures due to "notifyDone" not getting called
Summary: [Windows] Test Failures due to "notifyDone" not getting called
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Brent Fulgham
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-09-17 11:44 PDT by Brent Fulgham
Modified: 2015-01-05 15:33 PST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2013-09-17 11:44:51 PDT 
A large number of Windows tests are failing because "notifyDone" is not getting called during tests. These tests are being disabled for now, with investigation and resolution to be tracked by this bug.
Comment 1 Brent Fulgham 2013-09-17 11:56:29 PDT 
Tests were disabled in http://trac.webkit.org/changeset/
Comment 2 Radar WebKit Bug Importer 2013-09-17 11:57:21 PDT 
<rdar://problem/15011796>
Comment 3 Csaba Osztrogonác 2013-09-17 23:35:21 PDT 
Skip patches landed with the following commit message:
[Windows] Disable a number of failing tests to help the EWS system run more rapidly.

https://trac.webkit.org/changeset/155981
https://trac.webkit.org/changeset/155983

I think it was only a typo, and you meant buildbots, because Windows 
EWS bots don't run tests at all, they are build only EWS bots.

Otherwise we could speedup Windows EWS bots too ... but it seems the 
bots no. 1-7 are still dead and they only slow down the processing. :(
( https://lists.webkit.org/pipermail/webkit-dev/2013-September/025374.html )
Comment 4 Roger Fong 2013-09-18 01:13:54 PDT 
Ugh I thought I fixed those up a while back. EWS 8 and 9 were new EWS bots that I just set up recently, and they were simply cloned from, I think it was EWS 7. 

I'll take a look soon.
Comment 5 Brent Fulgham 2015-01-05 15:33:56 PST 
Note: 'notifyDone' is just a symptom that some earlier step in the test script is failing or timing out.