-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v21.x failing modules #1033
Comments
i believe maxogden → @max-mapper |
How can we check the logs? The |
@arcanis some of them might be related to the machine, yeah. I just want to make sure these timeouts aren't flaky on The ci.nodejs.org links are the ones with logs. |
AVA's failure is (most likely) a known issue, fixed in main but not yet released. |
I tried looking into what might be the problem in |
Timeout errors are usually machine issues since we run tests in parallel and the CPU can get stale causing timeouts. If this persists we can reduce/remove the concurrency - but it might affect the time elapsed of CITGM, which is undesirable. |
The ws failure is the same and on the same platform for all runs. On macOS, that test also fails on GHA sometimes. I would prefer not to do it, but I think I can skip it on macOS. |
I've just removed for the issue description the modules where the authors/maintainers confirmed the issues aren't related to the package itself. Thank you! I'll wait maintainers' input for the other ones. |
I've read all the lists again and removed the ones failing with timeout, which tends to be a machine issue and I've created a PR to skip the non-machine-related failing on Node.js 21. #1035 |
Closing in favour of #1060 |
The last 3 runs failed on Node.js 21. I've run against v21.x just to confirm it's nothing related to the v21.3.0 proposal
Modules:
citgm.jest-v29.7.0 #1032
citgm.ember-cli-v5.4.1 - @stefanpenner, @rwjblue, @Turbo87, @kellyselden
citgm.yeoman-generator-v7.1.1 - @SBoudrias, @sindresorhus
citgm.nan-v2.18.0 - @nodejs/addon-api
citgm.q-v1.5.1 - @kriskowal
The text was updated successfully, but these errors were encountered: