test(instr-undici): fix TAV failures with Node.js 14 and 16 #2111
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test all versions (TAV) tests were failing with Node.js 14 and 16
because of subtle behaviour changes in socket end handling in
Node.js and undici for a test that tries a bogus request. This
restores earlier work-around code mistakenly removed in #2085.
Since #2085, TAV tests for Node.js 14 and 16 started failing. E.g.: https://github.com/open-telemetry/opentelemetry-js-contrib/actions/runs/8724672054/job/23935801386
Back in #2085 (comment) a similar issue with undici + older Node.js versions + this testing of a bogus request was hit and I mistakenly assumed it was the same issue. The workaround for that other issue did not fix this one. This PR restores the same/similar workaround.