RESOLVED CONFIGURATION CHANGED 69982
Windows WK2 MouseMoveAfterCrash API test failing 
https://bugs.webkit.org/show_bug.cgi?id=69982
Summary Windows WK2 MouseMoveAfterCrash API test failing
Simon Fraser (smfr)
Reported 2011-10-12 18:31:39 PDT
http://build.webkit.org/builders/Windows%207%20Release%20%28WebKit2%20Tests%29/builds/11691/steps/run-api-tests/logs/stdio These tests are failing: WebKit2.WebKit2.CanHandleRequest WebKit2.WebKit2.DocumentStartUserScriptAlertCrashTest WebKit2.WebKit2.HitTestResultNodeHandle WebKit2.WebKit2.InjectedBundleBasic WebKit2.WebKit2.LoadCanceledNoServerRedirectCallback WebKit2.WebKit2.MouseMoveAfterCrash WebKit2.WebKit2.ResponsivenessTimerDoesntFireEarly WebKit2.WebKit2.WebArchive
Attachments
Add attachment proposed patch, testcase, etc.
Jeff Miller
Comment 1 2011-10-14 12:56:20 PDT
These all appear to be timeout failures. Adding Adam Roben to cc list.
Jessie Berlin
Comment 2 2012-05-30 16:05:19 PDT
Looks like the timeouts are no longer happening, but MouseMoveAfterCrash is failing: Note: Google Test filter = WebKit2.MouseMoveAfterCrash [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from WebKit2 [ RUN ] WebKit2.MouseMoveAfterCrash ..\Tests\WebKit2\MouseMoveAfterCrash.cpp(91): error: JS expression: didMoveMouse() Actual: false Expected: true [ FAILED ] WebKit2.MouseMoveAfterCrash (246 ms) [----------] 1 test from WebKit2 (246 ms total) http://build.webkit.org/builders/Windows%207%20Release%20%28Tests%29/builds/24273/steps/run-api-tests/logs/stdio It may be the same cause as https://bugs.webkit.org/show_bug.cgi?id=72751.
Radar WebKit Bug Importer
Comment 3 2012-05-30 16:06:08 PDT
<rdar://problem/11561393>
Note You need to log in before you can comment on or make changes to this bug.