[Webkit-unassigned] [Bug 261820] New: JS test stress/proxy-set-failure-inline-cache.js.bytecode-cache is flaky

[bugzilla-daemon at webkit.org]

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

            Bug ID: 261820
           Summary: JS test
                    stress/proxy-set-failure-inline-cache.js.bytecode-cach
                    e is flaky
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at redhat.com

This one particular test stress/proxy-set-failure-inline-cache.js.bytecode-cache has been flaky for several months now. I've just been slow to create a bug report:

Running stress/proxy-set-failure-inline-cache.js.default
Running stress/proxy-set-failure-inline-cache.js.bytecode-cache
stress/proxy-set-failure-inline-cache.js.bytecode-cache: Exception: Error: Bad value: 0!
stress/proxy-set-failure-inline-cache.js.bytecode-cache: shouldBe at proxy-set-failure-inline-cache.js:4:24
stress/proxy-set-failure-inline-cache.js.bytecode-cache: @proxy-set-failure-inline-cache.js:35:13
stress/proxy-set-failure-inline-cache.js.bytecode-cache: global code at proxy-set-failure-inline-cache.js:36:3
stress/proxy-set-failure-inline-cache.js.bytecode-cache: Command '/home/jenkins/workspace/WebKit-JSC/label/ppc64le/WebKitBuild/Release/bin/jsc proxy-set-failure-inline-cache.js --useFTLJIT=false --useFunctionDotArguments=true --validateExceptionChecks=true --useDollarVM=true --maxPerThreadStackUsage=1572864 --useFTLJIT=true' failed
stress/proxy-set-failure-inline-cache.js.bytecode-cache: ERROR: Unexpected exit code: 3

This is with a cloop build. The test sometimes succeeds and sometimes fails on at least x86_64 and ppc64le runners. This is currently the only test in the entire stress testsuite that is flaky and I believe only the .bytecode-cache version of the test ever fails.

Let's see if I can reproduce the failure locally.

-- 
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/20230920/6d1e9421/attachment-0001.htm>