Skip to content

tools: filter V8 scripts for build toolchain#63069

Open
richardlau wants to merge 1 commit into
nodejs:mainfrom
richardlau:makev8
Open

tools: filter V8 scripts for build toolchain#63069
richardlau wants to merge 1 commit into
nodejs:mainfrom
richardlau:makev8

Conversation

@richardlau
Copy link
Copy Markdown
Member

Patch the build scripts for V8 when running the V8 CI for Linux on ppc64le and s390x to workaround inconsistencies between the nightly build toolchain used by V8 and the released versions that we use from the Linux distribution.

Refs: #62572 (comment)
Refs: https://github.com/ibmruntimes/v8-build/blob/49b55c036da148bd18b546f19b731a0fe92b6a33/bin/v8.sh#L62-L71
Refs: nodejs/build#4265


Opening this as separate from the V8 14.8 update as I want to cherry-pick it across to v26.x. The plan is to update clang and rustc on the RHEL machines and this patch should keep the V8 CI working on v26.x and main during the transition. Without this patch V8 CI would break on Linux on ppc64le and s390x when we update Rust to 1.88 as "adler" has been replaced with "adler2".

@richardlau richardlau added dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. dont-land-on-v25.x PRs that should not land on the v25.x-staging branch and should not be released in v25.x. labels May 1, 2026
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency. labels May 1, 2026
Patch the build scripts for V8 when running the V8 CI for Linux on
ppc64le and s390x to workaround inconsistencies between the nightly
build toolchain used by V8 and the released versions that we use from
the Linux distribution.

Signed-off-by: Richard Lau <richard.lau@ibm.com>
@richardlau
Copy link
Copy Markdown
Member Author

Several force pushes to satisfy the sh linter.

Test runs:

Copy link
Copy Markdown
Member

@targos targos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM.

I think the build fails because of 7d65f79. I need to remove the tests that use these deleted functions.

@richardlau richardlau added the commit-queue Add this label to land a pull request using GitHub Actions. label May 11, 2026
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels May 11, 2026
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/63069
✔  Done loading data for nodejs/node/pull/63069
----------------------------------- PR info ------------------------------------
Title      tools: filter V8 scripts for build toolchain (#63069)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     richardlau:makev8 -> nodejs:main
Labels     v8 engine, tools, needs-ci, dont-land-on-v22.x, dont-land-on-v24.x, dont-land-on-v25.x
Commits    1
 - tools: filter V8 scripts for build toolchain
Committers 1
 - Richard Lau <richard.lau@ibm.com>
PR-URL: https://github.com/nodejs/node/pull/63069
Refs: https://github.com/ibmruntimes/v8-build/blob/49b55c036da148bd18b546f19b731a0fe92b6a33/bin/v8.sh#L62-L71
Refs: https://github.com/nodejs/build/issues/4265
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/63069
Refs: https://github.com/ibmruntimes/v8-build/blob/49b55c036da148bd18b546f19b731a0fe92b6a33/bin/v8.sh#L62-L71
Refs: https://github.com/nodejs/build/issues/4265
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
--------------------------------------------------------------------------------
   ℹ  This PR was created on Fri, 01 May 2026 15:55:44 GMT
   ✔  Approvals: 2
   ✔  - Joyee Cheung (@joyeecheung) (TSC): https://github.com/nodejs/node/pull/63069#pullrequestreview-4213602852
   ✔  - Michaël Zasso (@targos) (TSC): https://github.com/nodejs/node/pull/63069#pullrequestreview-4214476644
   ✔  Last GitHub CI successful
   ✘  No full Jenkins CI runs detected
   ℹ  Last V8 CI on 2026-05-01T17:02:41Z: https://ci.nodejs.org/job/node-test-commit-v8-linux/7169/
- Querying data for job/node-test-pull-request/7169/
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/25675882689

@richardlau richardlau added the request-ci Add this label to start a Jenkins CI on a PR. label May 11, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 11, 2026
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

commit-queue-failed An error occurred while landing this pull request using GitHub Actions. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v24.x PRs that should not land on the v24.x-staging branch and should not be released in v24.x. dont-land-on-v25.x PRs that should not land on the v25.x-staging branch and should not be released in v25.x. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants