Bug 250851 – [GARDENING][ BigSur+ JSC ] stress/intl-enumeration.js (JSC-Tests) are constantly failing

• Status: REOPENED
• Component: JavaScriptCore

[Robert Jenner]

The following stress/intl-enumeration.js JSC-Tests are constantly failing on BigSur and Monterey Release:

stress/intl-enumeration.js.bytecode-cache
stress/intl-enumeration.js.default
stress/intl-enumeration.js.dfg-eager
stress/intl-enumeration.js.dfg-eager-no-cjit-validate
stress/intl-enumeration.js.eager-jettison-no-cjit
stress/intl-enumeration.js.ftl-eager
stress/intl-enumeration.js.ftl-eager-no-cjit
stress/intl-enumeration.js.ftl-eager-no-cjit-b3o1
stress/intl-enumeration.js.ftl-no-cjit-b3o0
stress/intl-enumeration.js.ftl-no-cjit-no-inline-validate
stress/intl-enumeration.js.ftl-no-cjit-no-put-stack-validate
stress/intl-enumeration.js.ftl-no-cjit-small-pool
stress/intl-enumeration.js.ftl-no-cjit-validate-sampling-profiler
stress/intl-enumeration.js.lockdown
stress/intl-enumeration.js.mini-mode
stress/intl-enumeration.js.no-cjit-collect-continuously
stress/intl-enumeration.js.no-cjit-validate-phases
stress/intl-enumeration.js.no-ftl
stress/intl-enumeration.js.no-llint

HISTORY:
https://results.webkit.org/?suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&test=stress%2Fintl-enumeration.js.bytecode-cache&test=stress%2Fintl-enumeration.js.default&test=stress%2Fintl-enumeration.js.dfg-eager&test=stress%2Fintl-enumeration.js.dfg-eager-no-cjit-validate&test=stress%2Fintl-enumeration.js.eager-jettison-no-cjit&test=stress%2Fintl-enumeration.js.ftl-eager&test=stress%2Fintl-enumeration.js.ftl-eager-no-cjit&test=stress%2Fintl-enumeration.js.ftl-eager-no-cjit-b3o1&test=stress%2Fintl-enumeration.js.ftl-no-cjit-b3o0&test=stress%2Fintl-enumeration.js.ftl-no-cjit-no-inline-validate&test=stress%2Fintl-enumeration.js.ftl-no-cjit-no-put-stack-validate&test=stress%2Fintl-enumeration.js.ftl-no-cjit-small-pool&test=stress%2Fintl-enumeration.js.ftl-no-cjit-validate-sampling-profiler&test=stress%2Fintl-enumeration.js.lockdown&test=stress%2Fintl-enumeration.js.mini-mode&test=stress%2Fintl-enumeration.js.no-cjit-collect-continuously&test=stress%2Fintl-enumeration.js.no-cjit-validate-phases&test=stress%2Fintl-enumeration.js.no-ftl&test=stress%2Fintl-enumeration.js.no-llint


The history is pretty clear pointing to the the revert at 257697@Main that appears to have caused these tests to fail.

[Radar WebKit Bug Importer]

<rdar://problem/104432972>

[EWS]

Test gardening commit 259104@main (a155b7e276ea): <https://commits.webkit.org/259104@main>

Reviewed commits have been landed. Closing PR #8847 and removing active labels.

[Robert Jenner]

Pull request: https://github.com/WebKit/WebKit/pull/8893

[Robert Jenner]

(In reply to Robert Jenner from comment #3)
> Pull request: https://github.com/WebKit/WebKit/pull/8893

Since we figured out what broke this, and how it was broken I have submitted a change to this test above. My knowledge of JSC tests is limited at best. So my change may not fix it. But I just thought I would try. So let's see what EWS does with it.

[EWS]

Committed 259237@main (8b53ef6d2244): <https://commits.webkit.org/259237@main>

Reviewed commits have been landed. Closing PR #8893 and removing active labels.

[Robert Jenner]

Re-opening for pull request https://github.com/WebKit/WebKit/pull/9006

[EWS]

Test gardening commit 259289@main (0214f5ed6d34): <https://commits.webkit.org/259289@main>

Reviewed commits have been landed. Closing PR #9051 and removing active labels.

[Robert Jenner]

(In reply to Robert Jenner from comment #6)
> Re-opening for pull request https://github.com/WebKit/WebKit/pull/9006

Unfortunately it appears that my attempted fix did not actually solve the issues with this test and the changes to the timezone database. So I have re-opened this bug and have skipped the test in: https://commits.webkit.org/259289@main