Bug 204755
| Summary: | Flaky JSC test: stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Aakash Jain <aakash_jain> |
| Component: | Tools / Tests | Assignee: | Paulo Matos <pmatos> |
| Status: | NEW | ||
| Severity: | Normal | CC: | aakash_jain, ap, guijemont, jbedard, jsc32, mark.lam, pmatos, saam, ticaiolima, webkit-bot-watchers-bugzilla, ysuzuki |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Aakash Jain
stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js seems flaky. In https://ews-build.webkit.org/#/builders/26/builds/552, the test failed in jscore-test step. However, in the immediately next retry step (jscore-test-rerun), it passed.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Aakash Jain
This test was added in https://trac.webkit.org/changeset/241655/webkit
Alexey Proskuryakov
This test run was ARMv7. Flakiness dashboard should be able to tell soon which ports are affected.
stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js.default: Killed
stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js.default: ERROR: Unexpected exit code: 137