[Webkit-unassigned] [Bug 225998] New: [ Catalina Release JSC] A large number of JSC test appear to be flaky failing

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 19 17:57:20 PDT 2021


https://bugs.webkit.org/show_bug.cgi?id=225998

            Bug ID: 225998
           Summary: [ Catalina Release JSC] A large number of JSC test
                    appear to be flaky failing
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: Jenner at apple.com

The following JSC test have started to flaky fail on Catalina Release JSC-Tests:

wasm.yaml/wasm/function-tests/basic-element.js.wasm-eager-jettison
wasm.yaml/wasm/js-api/test_Data.js.wasm-collect-continuously
wasm.yaml/wasm/references/externref_modules.js.wasm-eager
wasm.yaml/wasm/stress/memory-fence.js.wasm-air
wasm.yaml/wasm/stress/mutable-globals.js.wasm-b3
wasm.yaml/wasm/function-tests/basic-element.js.wasm-air
wasm.yaml/wasm/function-tests/stack-trace.js.default-wasm
wasm.yaml/wasm/js-api/test_Data.js.wasm-b3
wasm.yaml/wasm/js-api/test_Data.js.wasm-eager-jettison
wasm.yaml/wasm/references/is_null.js.wasm-b3
wasm.yaml/wasm/stress/js-wasm-call-many-return-types-on-stack-no-args.js.wasm-eager
wasm.yaml/wasm/stress/memory-fence.js.wasm-collect-continuously
wasm.yaml/wasm/stress/too-many-locals.js.default-wasm
wasm.yaml/wasm/function-tests/basic-element.js.wasm-slow-memory
wasm.yaml/wasm/function-tests/stack-trace.js.wasm-no-tls-context
wasm.yaml/wasm/function-tests/trap-from-start.js.default-wasm
wasm.yaml/wasm/js-api/test_Data.js.wasm-air
wasm.yaml/wasm/js-api/test_memory.js.wasm-slow-memory
wasm.yaml/wasm/references/externref_table_import.js.wasm-no-tls-context
wasm.yaml/wasm/function-tests/trap-from-start.js.wasm-no-tls-context
wasm.yaml/wasm/function-tests/trap-store.js.wasm-b3
wasm.yaml/wasm/js-api/test_memory.js.wasm-b3
wasm.yaml/wasm/js-api/test_memory.js.wasm-eager-jettison
wasm.yaml/wasm/lowExecutableMemory/exports-oom.js.default-wasm
wasm.yaml/wasm/js-api/test_memory.js.default-wasm
wasm.yaml/wasm/self-test/test_LowLevelBinary_uint16.js.wasm-b3
wasm.yaml/wasm/function-tests/memory-access-past-4gib.js.wasm-collect-continuously
wasm.yaml/wasm/js-api/test_memory.js.wasm-air
wasm.yaml/wasm/references/externref_modules.js.default-wasm
wasm.yaml/wasm/references/func_ref.js.wasm-air
wasm.yaml/wasm/function-tests/trap-load-2.js.wasm-no-tls-context
wasm.yaml/wasm/js-api/test_Data.js.wasm-no-tls-context
wasm.yaml/wasm/references/func_ref.js.default-wasm
stress/put-by-val-slow-put-array-storage.js.dfg-eager-no-cjit-validate
stress/arrowfunction-lexical-bind-arguments-non-strict-1.js.dfg-eager
stress/arrowfunction-lexical-bind-superproperty.js.dfg-eager

HISTORY:
https://build.webkit.org/#/builders/Apple-Catalina-Release-JSC-Tests?numbuilds=50


These failures started occurring at this test run:
https://build.webkit.org/#/builders/4/builds/1998

My guess is that either r277727, or r277725 caused this, as they both appear to have made changes to things with JSC.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210520/507f08c4/attachment.htm>


More information about the webkit-unassigned mailing list