Rich Trott
Rich Trott
> @Trott the timeout change has definitely helped on most configurations, and github CI, but [node-test-commit-freebsd](https://ci.nodejs.org/job/node-test-commit-freebsd/44875/) failed the same way two times in a row, the webcrypto job is not...
> I wonder if the "Build timed out (after 6 minutes)" part is a Jenkins thing or something. ` grep -r 'Build timed out' .` on the code base didn't...
> Found it in the Jenkins config: @nodejs/build I see that node-test-commit-linux has a timeout 20 times larger than FreeBSD (7200 compared to 360). I'm going to take the liberty...
> @Trott Similar to FreeBSD before, the `node-test-commit-arm-debug` build times out after 5 minutes. @panva I've increased the timeout to 12 minutes. https://github.com/nodejs/build/issues/3001 I didn't do it before resuming the...
@nodejs/citgm
> https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2075/ | failed hosts in CI | package | notes [edit freely] | |---|---|---| 8 | citgm.csv-parser-v2.3.1 | fix in master but not release /ping @shellscape 6 | citgm.serialport-v7.1.5...
I believe the csv-parser failures will go away once a new version of csv-parser is published. The fix for it is in master, but not in a release. /ping @shellscape
serialport is expected to work with master when 8.x comes out of beta. Not sure what the expected release date is. /ping @reconbot
For zeromq, from https://github.com/nodejs/node/pull/29504#issuecomment-534724551: > @rolftimmermans has a next generation version here that is on the roadmap to be merged back to master!