| Summary: | REGRESSION(259117@main?): [BigSur+ Debug JSC ] Multiple map/set JavaScript tests are constant failures with ERROR: Unexpected exit code: 139 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Jenner <jenner> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | keith_miller, webkit-bot-watchers-bugzilla, webkit-bug-importer, ysuzuki |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Robert Jenner
2023-01-25 18:49:46 PST
Other tests that started to fail at the same point, but don't appear to reference maps or set in their name are as follows: airjs-tests.yaml/stress-test.js.bytecode-cache airjs-tests.yaml/stress-test.js.default airjs-tests.yaml/stress-test.js.dfg-eager airjs-tests.yaml/stress-test.js.dfg-eager-no-cjit-validate airjs-tests.yaml/stress-test.js.eager-jettison-no-cjit airjs-tests.yaml/stress-test.js.ftl-eager airjs-tests.yaml/stress-test.js.ftl-eager-no-cjit-b3o1 airjs-tests.yaml/stress-test.js.ftl-no-cjit-b3o0 airjs-tests.yaml/stress-test.js.ftl-no-cjit-no-inline-validate airjs-tests.yaml/stress-test.js.ftl-no-cjit-no-put-stack-validate airjs-tests.yaml/stress-test.js.ftl-no-cjit-small-pool airjs-tests.yaml/stress-test.js.ftl-no-cjit-validate-sampling-profiler airjs-tests.yaml/stress-test.js.mini-mode airjs-tests.yaml/stress-test.js.no-cjit-validate-phases airjs-tests.yaml/stress-test.js.no-ftl airjs-tests.yaml/stress-test.js.no-llint wasm.yaml/wasm/v8/many-memories-no-trap-handler.js.wasm-eager-jettison While there is a fairly large range in-between test runs, with the most recent pass occurring at 259088@main, and the first failure occurring at the next test run after that which was 259117@main. It does appear that 259117@main does modify map and set: https://commits.webkit.org/259117@main I would think that would be a likely culprit? For some reason a new bug was filed to land the fix. *** This bug has been marked as a duplicate of bug 251191 *** |