NEW 204755
Flaky JSC test: stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js 
https://bugs.webkit.org/show_bug.cgi?id=204755
Summary Flaky JSC test: stress/incremental-marking-should-not-dead-lock-in-new-proper...
Aakash Jain
Reported 2019-12-02 10:18:08 PST
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
Comment 1 2019-12-02 10:20:19 PST
This test was added in https://trac.webkit.org/changeset/241655/webkit
Alexey Proskuryakov
Comment 2 2019-12-03 23:59:22 PST
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
Note You need to log in before you can comment on or make changes to this bug.