V8: v8tests.mjsunit/regress/regress-crbug-514081 failure on PPC BE

[mhdawson]

• Version: master
• Platform: PPC BE
• Subsystem: V8

Failure in latest nightly run:

https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=ppcbe-ubuntu1404,v8test=v8test/330/

=== mjsunit/regress/regress-crbug-514081 ===
Command: /home/iojs/build/workspace/node-test-commit-v8-linux/nodes/ppcbe-ubuntu1404/v8test/v8test/deps/v8/out/ppc64.release/d8 --test --random-seed=-1860260574 --nohard-abort --nodead-code-elimination --nofold-constants /home/iojs/build/workspace/node-test-commit-v8-linux/nodes/ppcbe-ubuntu1404/v8test/v8test/deps/v8/test/mjsunit/mjsunit.js /home/iojs/build/workspace/node-test-commit-v8-linux/nodes/ppcbe-ubuntu1404/v8test/v8test/deps/v8/test/mjsunit/regress/regress-crbug-514081.js
exit code: -9
--- CRASHED ---

===
=== 1 tests failed
=== 1 tests CRASHED

[mhdawson]

Re-run to see if it is intermittent or persistent https://ci.nodejs.org/job/node-test-commit-v8-linux/334/

Seem to be having timeout problems doing checkouts, will have to wait until nightly runs to get data point on intermittent or consistent.

[mhdawson]

FYI @jbajwa

[mhdawson]

Latest v8 CI run was green, so failure must be intermittent.

https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=ppcbe-ubuntu1404,v8test=v8test/338/

[jbajwa]

yes, seems to be intermittent, I cannot reproduce the failure.

[bnoordhuis]

The test probably got terminated by the kernel's OOM killer. It tries to create a 2 GB ArrayBuffer and exit code -9 means it was terminated by a SIGKILL signal, which is the signal the OOM killer sends.

Didn't we have a similar issue a few months back?

[mhdawson]

Yes found this #6678

[mhdawson]

Looks like that floating patch got dropped along the way somewhere

[mhdawson]

Putting together PR to re-float patch

v8 CI test run here: https://ci.nodejs.org/job/node-test-commit-v8-linux/347/