Skip to content

build: run QUIC CI for V8 changes - #66602

Open
inoway46 wants to merge 1 commit into
nodejs:mainfrom
inoway46:quic-ci-v8-changes
Open

build: run QUIC CI for V8 changes#66602
inoway46 wants to merge 1 commit into
nodejs:mainfrom
inoway46:quic-ci-v8-changes

Conversation

@inoway46

@inoway46 inoway46 commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Add deps/v8/** to the QUIC workflow's PR path filter so V8 updates trigger its build and tests.

The V8 15.5 update did not trigger QUIC CI, allowing the SetPrototypeV2 compilation failure to go undetected.

Refs: #66537
Refs: https://github.com/nodejs/node/actions/runs/37675498427/job/112978479932

@inoway46
build: run QUIC CI for V8 changes
486e979 
Add deps/v8/** to the QUIC workflow's pull request path filter so
V8 updates trigger its build and tests.

Assisted-by: Codex
Signed-off-by: inoway46 <inoueyuya416@gmail.com>
@nodejs-github-bot

nodejs-github-bot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/actions

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Oct 8, 2026
@inoway46
inoway46 marked this pull request as ready for review October 8, 2026 12:57
@richardlau

richardlau commented Oct 8, 2026

Copy link
Copy Markdown
Member

The V8 15.5 update did not trigger QUIC CI, allowing the SetPrototypeV2 compilation failure to go undetected.

Was that fixed? It caused the QUIC CI to fail for #66569 and I was asked if it was due to the changes there or not (sounds like not).

@inoway46

inoway46 commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

Not yet. I’m currently investigating the compilation failure and testing a local build. It appears to be unrelated to #66569.

@inoway46 inoway46 mentioned this pull request Oct 8, 2026
Open
@inoway46

inoway46 commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

I've opened #66603 with a fix for the QUIC build failure.

@pimterry

pimterry commented Oct 8, 2026

Copy link
Copy Markdown
Member

Very happy for this to be enabled to help keep the QUIC build green, but QUIC is complicated and still quite rough around the edges, so you might run into flakes etc if we're running these tests more frequently.

Probably not a problem as long as you're aware and willing to take the risk. If that does become an issue at all do feel free to disable it again, just ping @nodejs/quic and we'll dig into anything that breaks.

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

Reviewers

@richardlau richardlau richardlau approved these changes

Assignees

No one assigned

Labels

meta Issues and PRs related to the general management of the project.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@inoway46 @nodejs-github-bot @richardlau @pimterry