Repository navigation
Conversation
|
Review requested:
|
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). |
|
Not yet. I’m currently investigating the compilation failure and testing a local build. It appears to be unrelated to #66569. |
|
I've opened #66603 with a fix for the QUIC build failure. |
|
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. |
Use SetPrototype when creating application options and transport parameter objects. V8 15.5 removed the deprecated SetPrototypeV2 wrapper, which delegated to SetPrototype, breaking QUIC builds. Assisted-by: Codex Signed-off-by: inoway46 <inoueyuya416@gmail.com> PR-URL: #66603 Refs: #66537 Refs: #66602 Reviewed-By: Tim Perry <pimterry@gmail.com> Reviewed-By: Richard Lau <richard.lau@ibm.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de>
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>
486e979 to
c7f7eef
Compare
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
SetPrototypeV2compilation failure to go undetected.Refs: #66537
Refs: https://github.com/nodejs/node/actions/runs/37675498427/job/112978479932