-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
build: define NODE_EXPERIMENTAL_QUIC in mkcodecache and node_mksnapshot #34454
Conversation
Custom build with --experimental-quic (pending) https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/15490/ |
We should try to fix those reverts before landing this so we don't have to revert them. I'll be able to take a look tomorrow |
Not sure why this PR would expose something like this, but here’s a fix: #34460 |
Once #34460 lands, the revert shouldn't be necessary and this otherwise LGTM |
Otherwise the build would fail with `./configure --experimental-quic --ninja` as the list of per-Environment values would not match and the code cache builder would not generate code cache for the quic JS sources. This is more or less a band-aid - a proper fix would be to aggregate these flags into something that can be included by all these different binary targets. See nodejs#31074.
Rebased. @nodejs/quic PTAL, thanks! |
CI: https://ci.nodejs.org/job/node-test-pull-request/32466/ (:green_heart:) |
Custom build with --experimental-quic (pending) https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/15520/ (:green_heart:) |
Fast track ? |
Otherwise the build would fail with `./configure --experimental-quic --ninja` as the list of per-Environment values would not match and the code cache builder would not generate code cache for the quic JS sources. This is more or less a band-aid - a proper fix would be to aggregate these flags into something that can be included by all these different binary targets. See #31074. PR-URL: #34454 Fixes: #34435 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Landed in f4f191b |
Otherwise the build would fail with `./configure --experimental-quic --ninja` as the list of per-Environment values would not match and the code cache builder would not generate code cache for the quic JS sources. This is more or less a band-aid - a proper fix would be to aggregate these flags into something that can be included by all these different binary targets. See #31074. PR-URL: #34454 Fixes: #34435 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Adding don't land labels for 10.x - 14.x as this is related to quic |
build: define NODE_EXPERIMENTAL_QUIC in mkcodecache and node_mksnapshot
Otherwise the build would fail with
./configure --experimental-quic --ninja
as the list of per-Environmentvalues would not match and the code cache builder would not generate
code cache for the quic JS sources. This is more or less a band-aid -
a proper fix would be to aggregate these flags into something
that can be included by all these different binary targets.
See #31074.
Fixes: #34435
Revert "src: refactor TimerWrap lifetime management"
This reverts commit 874460a.
@addaleax I have no idea why but it seems the TimerWrap lifetime management refactoring 874460a is also causing the build to fail a bunch of quic tests, crashing with
So I revereted it as well to make the tests pass
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes