Skip to content

Update node 8 version and pin nyc. Also added missing 9.x to ci-tests… - #49

Merged
UlisesGascon merged 1 commit into
jshttp:masterfrom
carpasse:ci/fix_test_in_node_8_and_9
Apr 29, 2024
Merged

UlisesGascon merged 1 commit into
jshttp:masterfrom
carpasse:ci/fix_test_in_node_8_and_9

Conversation

@carpasse

Copy link
Copy Markdown
Contributor

… action

closes #48
Similar fix as jshttp/http-errors#109

@carpasse
carpasse force-pushed the ci/fix_test_in_node_8_and_9 branch 2 times, most recently from 588707d to 474b678 Compare March 27, 2024 17:01
@carpasse

Copy link
Copy Markdown
Contributor Author

Node 9 seems to fail. I am investigating

@carpasse
carpasse force-pushed the ci/fix_test_in_node_8_and_9 branch from 474b678 to 2a045c5 Compare March 28, 2024 12:27
@carpasse

Copy link
Copy Markdown
Contributor Author

I think there is a bug in node 9 http_parser or on the http server. Which is the reason why the tests are failing on node 9. I've tried to make it fail differently but nothing I do causes the error to be propagated to the on-finished handler

I've removed node 9 form the ci-tests gh action as it is currently and I will try to investigate a bit further separately.

@wesleytodd

Copy link
Copy Markdown
Member

Ah, that does ring a bell for me. That said, we should probably leave a comment in the yaml file to the reason it is excluded or something to prevent future confusion. Future really is we remove all this as we drop support with the next major, but that will be a bit for this one I think.

@carpasse
carpasse force-pushed the ci/fix_test_in_node_8_and_9 branch from 2a045c5 to 12be913 Compare March 28, 2024 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken tests for Node@8 and Node@9 #159

3 participants