I'm skipping the test on armv7 and mips for now. Please re-enable if needed when this failure has been investigated.
The test is skipped in r259530: <http://trac.webkit.org/r259530>.
Coppied from https://build.webkit.org/builders/JSCOnly%20Linux%20MIPS32el%20Release/builds/4769/steps/jscore-test/logs/stdio : Running stress/typed-array-subarray-can-throw-oom-error.js.default Running stress/typed-array-subarray-can-throw-oom-error.js.mini-mode stress/typed-array-subarray-can-throw-oom-error.js.default: Aborted stress/typed-array-subarray-can-throw-oom-error.js.default: ERROR: Unexpected exit code: 134 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.default Running stress/typed-array-subarray-can-throw-oom-error.js.no-llint stress/typed-array-subarray-can-throw-oom-error.js.mini-mode: Bus error stress/typed-array-subarray-can-throw-oom-error.js.mini-mode: ERROR: Unexpected exit code: 138 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.mini-mode Running stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-validate-phases stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-validate-phases: Bus error stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-validate-phases: ERROR: Unexpected exit code: 138 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-validate-phases Running stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-collect-continuously stress/typed-array-subarray-can-throw-oom-error.js.no-llint: Aborted stress/typed-array-subarray-can-throw-oom-error.js.no-llint: ERROR: Unexpected exit code: 134 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.no-llint Running stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-collect-continuously: Aborted stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-collect-continuously: ERROR: Unexpected exit code: 134 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.no-cjit-collect-continuously Running stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager-no-cjit-validate stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager: Aborted stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager: ERROR: Unexpected exit code: 134 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager Running stress/typed-array-subarray-can-throw-oom-error.js.eager-jettison-no-cjit stress/typed-array-subarray-can-throw-oom-error.js.eager-jettison-no-cjit: Bus error stress/typed-array-subarray-can-throw-oom-error.js.eager-jettison-no-cjit: ERROR: Unexpected exit code: 138 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.eager-jettison-no-cjit Running stress/may-exit-should-be-false-regexp-constant-folding.js.default stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager-no-cjit-validate: Bus error stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager-no-cjit-validate: ERROR: Unexpected exit code: 138 FAIL: stress/typed-array-subarray-can-throw-oom-error.js.dfg-eager-no-cjit-validate
The problem of this test on ARMv7 bot is that it is consuming more memory than available on device. It is being aborted with the following message: ``` SHOULD NEVER BE REACHED ../../Source/JavaScriptCore/heap/LocalAllocator.cpp(147) : void* JSC::LocalAllocator::allocateSlowCase(JSC::Heap&, JSC::GCDeferralContext*, JSC::AllocationFailureMode) ``` Given that, `skip if $memoryLimited` seems accurate for me.