| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
It would be good to have this fast-tracked! |
Sorry, something went wrong.
|
CI is just about there on this one, apart from the flakes of course. We still need another approval to merge though. |
Sorry, something went wrong.
Not seeing any flakes, but I'm seeing a Windows compilation failure that will prevent the Windows tests from running, so we'll definitely want to do a Resume Build once the rest of the CI finishes.
Yup. /ping @nodejs/modules-active-members |
Sorry, something went wrong.
|
@Trott that Windows failure has been coming up on every CI the past couple of days as far as I can tell. |
Sorry, something went wrong.
Didn't show up in node-daily-master last night or the night before. We certainly should be landing no code changes whatsoever if Windows CI isn't running. |
Sorry, something went wrong.
|
I believe it is only the windows 2019 build that has been failing. |
Sorry, something went wrong.
If it fails, then the next job (that actually runs the tests!) doesn't run. 😱 Fortunately, it looks like it's been succeeding a lot more than failing: https://ci.nodejs.org/job/node-compile-windows-debug/ The last machine in the CI run (debian9-docker-armv7) is finishing up now so we should be able to try a Resume Build pretty quickly and see what happens. |
Sorry, something went wrong.
|
Yes it's really hard with this many flakes to tell what is a genuine failure. I believe I may have also missed the failure at https://ci.nodejs.org/job/node-test-binary-windows-js-suites/29/ on that merge... I'm looking into this now as well, to see if I can include the fix in this PR. |
Sorry, something went wrong.
Fair. |
Sorry, something went wrong.
|
Windows CI rebuild: https://ci.nodejs.org/job/node-test-commit-windows-fanned/32010/ - It looks like es-module/test-cjs-esm-warn is a real failure, but I just saw it failing on master as well so I don't know if it's related to this PR. There were a lot of failures compiling in Windows today, I took a few machines offline and I believe it's mitigated for now. I haven't figured out what's happening yet, but it looks like a missing build dependency. |
Sorry, something went wrong.
|
I'm on the Windows rebuilds here too, no worries! Will cancel and run again due to a lint issue. |
Sorry, something went wrong.
|
(the two latest commits should fix the Windows regression that slipped through into master as well, as mentioned in #30802 (comment)) |
Sorry, something went wrong.
There was a problem hiding this comment.
test-cjs-esm-warn fix LGTM
Sorry, something went wrong.
|
@nodejs/collaborators This could use a second review an 👍 to fast-tracking so we can unbreak CI. PTAL if you're around right now? |
Sorry, something went wrong.
Whoops, never mind, I'm three minutes out of date, this has all the needed approvals and can land once we get a green/yellow CI. |
Sorry, something went wrong.
|
I tried to retrigger the build on the last suggestion, but can't tell if it's running against the right commit? Will stop pushing buttons now to avoid further interference, but hopefully we nearly there now. |
Sorry, something went wrong.
|
Ok, CI run seems like it's doing the right thing. Will keep an eye on it here. |
Sorry, something went wrong.
|
Hit another windows failure on the other PR that landed today... that seems itself to be a new flake...! Is there a way we can just run the Windows CI build? |
Sorry, something went wrong.
Sorry, something went wrong.
|
@guybedford you can go to https://ci.nodejs.org/job/node-test-commit-windows-fanned/ and click "Build with Parameters". |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm, +1 to fast-track
Sorry, something went wrong.
|
Seems there was a Windows issue brought in on #30678 which the timeout was possibly masking. We should either revert that PR or add a fix. I'm running a local windows build now, but don't have much more time here right now. |
Sorry, something went wrong.
We have a successful Windows CI on the most recent version of this PR so I'd be inclined to land and address this other issue subsequently if it recurs. Just waiting for the docker build to start and finish at this point.... |
Sorry, something went wrong.
|
These GitHub summaries being out of sync always fool me. Yes it seems we are good. |
Sorry, something went wrong.
PR-URL: #30802 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: #30802 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: #30802 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: #30802 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
| Back | FazBrowse Home | New Git URL |
The CI for #30336 was run before the linting change to ensure the use of primordials causing the commit at 1549c8e to fail.
This should resolve that issue.
Checklist