citgm
citgm copied to clipboard
nodejs
Canary in the Gold Mine
##### Checklist - [x] `npm test` passes - [x] contribution guidelines followed [here](https://github.com/nodejs/citgm/blob/HEAD/CONTRIBUTING.md)
From https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=osx11/: ``` 11:00:40 + curl -O https://nodejs.org/download/release/v20.10.0/node-v20.10.0-darwin-x64.tar.gz ... 11:00:49 /var/folders/1l/nz78mlkn2bx3p52l61053yqm0000gp/T/jenkins12141042854684170859.sh: line 34: /Users/iojs/build/workspace/citgm-smoker-nobuild/node/bin/node: Bad CPU type in executable ``` I also noticed that it works on [test-nearform-macos11.0-arm64-1](https://ci.nodejs.org/computer/test-nearform-macos11.0-arm64-1) - from...
##### Checklist - [x] `npm test` passes - [x] contribution guidelines followed [here](https://github.com/nodejs/citgm/blob/HEAD/CONTRIBUTING.md)
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 * v21.3.0 proposal (1) https://ci.nodejs.org/job/citgm-smoker/3350/ * v21.3.0 proposal...
##### Checklist - [x] `npm test` passes - [x] contribution guidelines followed [here](https://github.com/nodejs/citgm/blob/HEAD/CONTRIBUTING.md) ##### Related - Closes https://github.com/nodejs/citgm/issues/1017 Co-authored-by: Ethan Arrowood
I’d like to add Next.js to CITGM. It uses `pnpm` to install dependencies, and before its tests can run it needs to be built. See https://github.com/vercel/next.js/blob/canary/contributing/core/developing.md. Can we add support...
We've experienced some issues on v21.x when running the suite on `osx11` Ref: * https://ci.nodejs.org/job/citgm-smoker/3351/nodes=osx11/testReport/junit/(root)/citgm/through2_v4_0_2/ * https://ci.nodejs.org/job/citgm-smoker/3364/nodes=osx11/testReport/junit/(root)/citgm/through2_v4_0_2/ Can we skip an environment in a specific version? v21.x >=
readable-stream is technically node core streams wrapped as a module. If we are not able to run this... well, we have problems. I Have a suspect these are passing now....
This seems like an important one to get working. I guess if we’ve been skipping it since Node 12 then it’s de facto already removed, but it feels like one...