Bug 261820 – JS test stress/proxy-set-failure-inline-cache.js.bytecode-cache is flaky

• Status: NEW
• Component: JavaScriptCore

[Michael Catanzaro]

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: [e-mail]: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 [e-mail]: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.

[Michael Catanzaro]

(In reply to Michael Catanzaro from comment #0)
> Let's see if I can reproduce the failure locally.

I can reproduce. When I run the test locally it always fails with the above error. But also, all of the subtests .lockdown, .mini-mode, and .default fail in addition to .bytecode-cache.

[Radar WebKit Bug Importer]

<rdar://problem/116121402>