-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Bug: CI fails because it can't set up Node #6463
Copy link
Copy link
Closed
Description
The current behavior
Unexpectedly, CI fails while fetching NodeJS with a 522 error (timeout):
log: https://github.com/facebook/lexical/actions/runs/10107570076/job/27951708511?pr=6367
According to the log, the builds use the cached version from actions/node-versions and skip the download step if the version (i.e., 18.18.0) can be found in manifest.
But 18.18.0 for arm64 is not on this list. So we fetch it directly from Node.js:
And there is possibility of hitting rate limit when downloading from dist:
...there is possibility of hitting rate limit when downloading from dist
https://github.com/actions/setup-node#supported-version-syntax
which is leading timeout with 522 unexpectedly.
The expected behavior
No failures while setting up node on CI.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels