| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
|
Fast-track has been requested by @danielleadams. Please 👍 to approve. |
Sorry, something went wrong.
PR-URL: #42299 Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
|
Belated +1 to this PR and unblocking the release. It looks like windows-2022 has been in the matrix for Node.js 16 since 6775958 (Sept 2021) - so it was presumably passing on this configuration up until the recent actions update (actions/runner-images@c0d5701, mentioned in #42200 (comment))? I am just wondering if we should open an issue to track/identify this problem? I could see the outcome potentially being that we can add it back when/if a future actions update fixes it? Or maybe opt to update BUILDING.md as I think(?) it is implicitly stating that this would be a supported toolchain for Node.js 16? |
Sorry, something went wrong.
Sure. I also tried to report the bug to MSVC team yesterday, but report bug entrance only in visual studio on windows which I don't have for now. |
Sorry, something went wrong.
PR-URL: #42299 Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
I've already reported this bug to MSVC team issue ticket |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Removes GitHub actions run on the windows-2022 virtual environment for v16.x release line. (As mentioned here: #42200) (cc @nodejs/releasers, @gengjiawen)