204755 2019-12-02 10:18:08 -0800 Flaky JSC test: stress/incremental-marking-should-not-dead-lock-in-new-property-transition.js 2020-04-21 12:11:27 -0700 1 1 1 Unclassified WebKit Tools / Tests Other Unspecified Unspecified NEW P2 Normal --- 1 aakash_jain pmatos aakash_jain ap guijemont jbedard jsc32 mark.lam pmatos saam ticaiolima webkit-bot-watchers-bugzilla ysuzuki oldest_to_newest 1594674 0 aakash_jain 2019-12-02 10:18:08 -0800 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. 1594676 1 aakash_jain 2019-12-02 10:20:19 -0800 This test was added in https://trac.webkit.org/changeset/241655/webkit 1595393 2 ap 2019-12-03 23:59:22 -0800 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