-
-
Notifications
You must be signed in to change notification settings - Fork 3k
chore: Fix tests #5320
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
chore: Fix tests #5320
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧪
I don't have permissions to merge, not sure if this is by design for the main repo, just FYI. I'm OK merging these changes :) Merging is blocked |
I think VoxPelli was looking into getting you those permissions. In the meantime I can merge it 👍 |
@mark-wiemer @JoshuaKGoldberg I tried to improve it now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses test failures on Node 20.19.0 by restricting the CI matrix to supported patch versions and adds a manual trigger for the workflow.
- Added
workflow_dispatch
to allow manual runs of the test workflow. - Pinned the Node 20 version to 20.18.3 and Node 22 to 22.11.0 in the test matrix.
Comments suppressed due to low confidence (1)
.github/workflows/mocha.yml:71
- [nitpick] Consider using a semver range (e.g.,
'18, >=20.18.3 <20.19, 22.11.0'
) instead of a fixed patch version to avoid needing updates for each new patch release.
node-versions: '18,20.18.3,22.11.0'
PR Checklist
status: accepting prs
Overview
When moving to Node 20.19.0, we are seeing consistent test failures, and it's unclear why. For now, it's best to clarify that we only support Node 20.18.3 and continue investigation on issues with Node ^20.19.0 separately.
We will still have flaky issues with Windows 20.18.3 as clarified in #5052. I had to mark this PR as "fixing" the issue in order to pass a separate PR validation. I will reopen #5052 after this PR is merged for further investigation.