Skip to content

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Dec 7, 2024

In #22987 I added a new veriant of the test_nodejs_sockets_echo test and chose the next consecutive port number, but it seems that each test ends up using two ports numbers so this could conflicted with the tests that were using both the previous and next number in the sequence (59164 and 59166).

In emscripten-core#22987 I added a new veriant of the test_nodejs_sockets_echo test
and chose the next consecutive port number, but it seems that each
test ends up using two ports numbers so this could conflicted with
the tests that were using both the previous and next number in the
sequence (59164 and 59166).
@sbc100 sbc100 requested a review from kripken December 7, 2024 18:54
@sbc100
Copy link
Collaborator Author

sbc100 commented Dec 7, 2024

Landing TBR to fix the ongoing test flakiness.

@sbc100 sbc100 merged commit c08204e into emscripten-core:main Dec 7, 2024
14 of 28 checks passed
@sbc100 sbc100 deleted the fix_socket_flakyness branch December 7, 2024 19:29
sbc100 added a commit to sbc100/emscripten that referenced this pull request Dec 9, 2024
In emscripten-core#22987 I added a new veriant of the test_nodejs_sockets_echo test and
chose the next consecutive port number, but it seems that each test ends
up using two ports numbers so this could conflicted with the tests that
were using both the previous and next number in the sequence (59164 and
59166).
hedwigz pushed a commit to hedwigz/emscripten that referenced this pull request Dec 18, 2024
In emscripten-core#22987 I added a new veriant of the test_nodejs_sockets_echo test and
chose the next consecutive port number, but it seems that each test ends
up using two ports numbers so this could conflicted with the tests that
were using both the previous and next number in the sequence (59164 and
59166).
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.

1 participant