Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: skip v8's regress/regress-1320641 on ppc64 and s390x #48814

Closed
wants to merge 1 commit into from

Conversation

joyeecheung
Copy link
Member

This breaks Node.js's V8 CI. We could turn them back on when it gets fixed on those platforms.

cc @nodejs/platform-s390 @nodejs/platform-ppc

This breaks Node.js's V8 CI. We could turn them back on when it
gets fixed on those platforms.
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/gyp
  • @nodejs/v8-update

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. v8 engine Issues and PRs related to the V8 dependency. labels Jul 17, 2023
@richardlau
Copy link
Member

cc @nodejs/platform-s390 @nodejs/platform-ppc

FWIW the failure on our CI looks like
e.g. https://ci.nodejs.org/job/node-test-commit-v8-linux/5461/nodes=rhel8-s390x,v8test=v8test/consoleFull

10:38:08 === mjsunit/regress/regress-1320641 ===
10:38:08 --- stdout ---
10:38:08 /home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/test/mjsunit/regress/regress-1320641.js:8: RangeError: Array buffer allocation failed
10:38:08   const xs = new Uint16Array(3775336418);
10:38:08              ^
10:38:08 RangeError: Array buffer allocation failed
10:38:08     at new ArrayBuffer (<anonymous>)
10:38:08     at new Uint16Array (<anonymous>)
10:38:08     at foo (/home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/test/mjsunit/regress/regress-1320641.js:8:14)
10:38:08     at /home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/test/mjsunit/regress/regress-1320641.js:12:1
10:38:08 Command: /home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/out.gn/s390x.release/d8 --test /home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/test/mjsunit/mjsunit.js /home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/test/mjsunit/regress/regress-1320641.js --random-seed=96903975 --nohard-abort --testing-d8-test-runner --allow-natives-syntax
10:38:08 
10:38:08 ===
10:38:08 === 1 tests failed
10:38:08 ===

@joyeecheung
Copy link
Member Author

Maybe this is a better fix https://chromium-review.googlesource.com/c/v8/v8/+/4689686

@joyeecheung joyeecheung added the blocked PRs that are blocked by other issues or PRs. label Jul 17, 2023
@miladfarca
Copy link
Contributor

miladfarca commented Jul 17, 2023

Not specific to ppc/s390. You can limit your virtual memory to 8 Gb with ulimit -Sv 8000000 and it should fail on any platform (Fails on x64 with a different msg as they have sandbox enabled).

@joyeecheung
Copy link
Member Author

Superseded by #48830

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked PRs that are blocked by other issues or PRs. build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants