Bug 99432
Summary: | PerformanceTest DOM/DOMWalk.html is failing on Chromium Win perf | ||
---|---|---|---|
Product: | WebKit | Reporter: | Shinya Kawanaka <shinyak> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | danakj, dstockwell, jchaffraix, msaboff, peter, rniwa |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Shinya Kawanaka
Running DOM/DOMWalk.html (31 of 102)
runFunction returned a non-positive value: 0
runFunction returned a non-positive value: 0
runFunction returned a non-positive value: 0
runFunction returned a non-positive value: 0
runFunction returned a non-positive value: 0
FAILED
Finished: 9.610000 s
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Shinya Kawanaka
Started in this range.
http://build.webkit.org/builders/Chromium%20Win%20Release%20%28Perf%29/builds/3836
I've tried to roll out r131403, but it is still failing. (I've rolled out the 'roll out')
Shinya Kawanaka
I don't have Windows machine now, so I cannot check...
Julien Chaffraix
Ryosuke told me this is a known bug where a test returns a negative value making it fail even if it actually didn't. CC'ing him in case I missed something.
Ryosuke Niwa
*** This bug has been marked as a duplicate of bug 104866 ***