Summary: | Windows WK2 MouseMoveAfterCrash API test failing | ||
---|---|---|---|
Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | aroben, bdakin, bfulgham, bweinstein, jberlin, jeffm, sam, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar, MakingBotsRed, Regression |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://build.webkit.org/builders/Windows%207%20Release%20%28WebKit2%20Tests%29/builds/11691/steps/run-api-tests/logs/stdio | ||
Bug Depends on: | |||
Bug Blocks: | 70136 |
Description
Simon Fraser (smfr)
2011-10-12 18:31:39 PDT
These all appear to be timeout failures. Adding Adam Roben to cc list. 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. |