You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just running the tests with parallelism/multiple jobs was able to trigger a test failure for the test case test-multi-poll.c but if you test without parallelism then the test will pass.
I have found that changing the LISTEN_PORT will resolve this issue... Therefore I think it is most likely to be a conflict with some other wepoll test or socket activity on the system. Possibly test-connect-success-events and/or test-udp-pings both of which seem to have PORT defines for 12345, the same as test-multi-poll.c
The text was updated successfully, but these errors were encountered:
Just running the tests with parallelism/multiple jobs was able to trigger a test failure for the test case test-multi-poll.c but if you test without parallelism then the test will pass.
I have found that changing the LISTEN_PORT will resolve this issue... Therefore I think it is most likely to be a conflict with some other wepoll test or socket activity on the system. Possibly test-connect-success-events and/or test-udp-pings both of which seem to have PORT defines for 12345, the same as test-multi-poll.c
The text was updated successfully, but these errors were encountered: