Bug 98192
| Summary: | [chromium] js-test-pre.js is flaky on Win Debug | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ojan Vafai <ojan> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | abarth, arv |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 98274 | ||
| Bug Blocks: | |||
Ojan Vafai
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#showExpectations=true&revision=130150&tests=fast%2Fjs%2Fpost-message-numeric-property.html
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ojan Vafai
fast/js/dfg-cross-global-object-inline-new-array-with-elements.html also seems flaky in a similar way to fast/js/post-message-numeric-property.html (message ordering). Seems likely a race in js-test-pre.js or with onload handlers?
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#showExpectations=true&tests=fast%2Fjs%2Fdfg-cross-global-object-inline-new-array-with-elements.html
Erik Arvidsson
The setTimeout call looks suspicious. It might call notifyDone too early. I'll refactor.
Erik Arvidsson
(In reply to comment #2)
> The setTimeout call looks suspicious. It might call notifyDone too early. I'll refactor.
That was for dfg-cross-global-object-inline-new-array-with-elements.js
Stephen Chenney
Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.