Repository navigation
Tracking issue for Fastify regressions #49600
Description
Activity
A few notes that we have already fixed a few problems that broke Fastify, so this is not relatively new:
cc @ShogunPanda
I don't think this is related to
httpornetmodule but something is preventing Node to close. In couple of weeks once I finish traveling I'll look into this.Most of those issues are caused by #49344.
However even after disabling code coverage, CITGM is still failing: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3272/.
This might be partially due to some of our CITGM machines, but it's something that should be investigated.
Currently, Fastify tests are failing on v20 on CITGM.
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3224/nodes=fedora-latest-x64/testReport/junit/(root)/citgm/fastify_v4_22_2/
The tests that are failing to shut down the process are:
The test passes, but it times out when it's trying to shut down the process.
This might be due to changes in the keep-alive logic in v20. It's entirely possible that those changes unveiled some bugs elsewhere, but we are having a hard time investigating this because it happens only in CI.
The other option is that it's a bug in the testing harness (tap), or coverage collection.
This might be the case because we are seeing some flaky tests in CITGM too: https://github.com/nodejs/citgm/actions/runs/6143382259/job/16666721399#step:14:618.