Uh oh!
There was an error while loading. Please reload this page.
esm: fix chain advances when loader calls next<HookName> multiple times - #43303
Conversation
Review requested:
|
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as resolved.
This comment was marked as resolved.
3cf8f28 to
9099755CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
910d4ff to
4a2969bCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
JakobJingleheimer
commented
Jun 5, 2022
@tniessen is the current test failure something I can ignore? I can’t see how it’s related (and it affects only 1 system). Rich and I both tried re-triggering it, but it timed out again both times. |
nodejs-github-bot
commented
Jun 5, 2022
nodejs-github-bot
commented
Jun 5, 2022
nodejs-github-bot
commented
Jun 5, 2022
tniessen
commented
Jun 5, 2022
@JakobJingleheimer No, sorry. As long as nobody fixes the underlying issue, we'll have to keep retrying. |
Sorry, are you saying it's signalling a legit problem in the PR or there is a problem in the test? If the former, do we have any idea where/why the test has a problem? (Is it tracked? I might try to fix it) If the latter, can I just add the label and otherwise ignore it? |
nodejs-github-bot
commented
Jun 5, 2022
Trott
commented
Jun 5, 2022
Looks like it passed on the 4th run.
The commit queue won't land something if a GitHub Action failed. |
aduh95
commented
Jun 5, 2022
What label? In order for a PR to land, all the GitHub Actions CIs must be green, and depending if the PR content affects the The ASan CI has been very flaky lately (https://github.com/nodejs/node/issues?q=is%3Aissue+asan+is%3Aopen+label%3Aflaky-test), which is a pain but as Tobias said, it's something we have to suffer until someone addresses the underlying issue(s). |
JakobJingleheimer
commented
Jun 5, 2022
Oh, I was thinking Ah, cool; I'll wait for the remaining actions to finish. Thanks! |
nodejs-github-bot
commented
Jun 5, 2022
Landed in 765666a |
JakobJingleheimer
commented
Jun 5, 2022
Backport blocked by #42623 (which is itself blocked for backport) |
PR-URL: #43303 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: #43303 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: #43303 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: #43303 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: nodejs/node#43303 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
fixes#43238