Michaël Zasso
Michaël Zasso
Failure from https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3334/nodes=rhel8-x64/ ``` # Subtest: test/connect-timeout.js # Subtest: priotorise socket errors over timeouts 1..1 not ok 1 - should be equal --- compare: === at: line: 16 column: 9...
@RafaelGSS You used the wrong job. It should be https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-pipeline/
We need to revisit this. Another regression appeared in v21.7.0 and would have been caught by undici.
https://github.com/nodejs/citgm/actions/runs/6298376266
Tests don't pass with Node.js 20.x
You can do it locally with `citgm express`. Error is: ``` error: | with strict option error: | when undefined error: | should 400 on primitives: error: | Error: expected...
Full CI: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-pipeline/239/
Actual error is: ``` 11:16:22 /var/folders/qn/tzmmkdsj1b1__zpsd02jn7x80000gp/T/jenkins11590088253155342208.sh: line 34: /Users/iojs/build/workspace/citgm-smoker-nobuild/node/bin/node: Bad CPU type in executable ``` Tracked by https://github.com/nodejs/citgm/issues/1042 This can land.
You can already use `citgm-all` to run on multiple packages: `citgm-all --includeTags package1 package2 ...`
Isn't it the purpose of the "maintainers" field?