ava@v5.3.1 not working on Node v21.x
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
Hi @sindresorhus, @novemberborn I noticed you're listed as maintainer for ava so I'd like to bring to your attention that ava@v5.3.1 tests have been failing across different systems on v21.x. Feel free to loop in more contributors that you think may help.
Here a failed run for reference:
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3318/testReport/
As you can see on this run jose is failing on two different nodes, but at the same time I see that a lot of nodes are skipped (["14", "ppc", "win32", "x86", "rhel", "aix", "ia32"]), so probably the problem can have a bigger scope. Can you please help us to debug the issue? I'm not sure if this is related to the new Node version or something inside the package.
In the last days we had timeout issues which has been fixed by #1003, but now this new issue looks unrelated to the timeout
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked citgm-smoker test report for AVA v5.3.1 on Node v21.x and compare the failures across the listed systems. Review the context around #1003 to distinguish this report from the earlier timeout issue. Done means identifying whether the failure is caused by Node v21.x or the package and documenting a reproducible scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100