nodeSolidServer / nodeSolidServer/node-solid-server
Tests are not running anymore in CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Tests are not running anymore in CI
There is no issue locally. Issue is the same with c8 or nyc with and without --experimental-require-module (not needed anymore the require module has been backported in node 20.19.0 and 22.14.0)
This is an example https://github.com/nodeSolidServer/node-solid-server/tree/refs/heads/fix/issue%231798
branch fix/issue#1798
Run npm run nyc
> solid-server@5.8.5 nyc
> cross-env NODE_TLS_REJECT_UNAUTHORIZED=0 nyc --reporter=text-summary mocha --recursive test/integration/ test/unit/
(node:2062) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: EEXIST: file already exists, mkdir '/home/runner/work/node-solid-server/node-solid-server/test/resources/accounts/single-user'] {
errno: -1[7](https://github.com/nodeSolidServer/node-solid-server/actions/runs/14363534639/job/40270776945#step:13:8),
code: 'EEXIST',
syscall: 'mkdir',
path: '/home/runner/work/node-solid-server/node-solid-server/test/resources/accounts/single-user'
}
Node.js v22.14.0
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 npm run nyc command and the example branch fix/issue#1798. Reproduce the failure in CI on Node.js 22.14.0, then inspect how test/resources/accounts/single-user is created during the integration and unit test run. Done means the CI test command completes without the EEXIST error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100