-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket tests 2301, 2302 flaky on Windows (mingw-w64) #13692
Comments
This seems to be an expected LF vs generated CRLF issue for 2305. |
vszakats
changed the title
WebSocket 2305 and 2301 tests flaky on Windows (mingw-w64)
WebSocket test 2305 fail and 2301 flaky on Windows (mingw-w64)
May 17, 2024
vszakats
added a commit
to vszakats/curl
that referenced
this issue
May 17, 2024
Ref: curl#13692 Closes #xxxxx
vszakats
added a commit
to vszakats/curl
that referenced
this issue
May 17, 2024
Ref: curl#13692 Closes #xxxxx
vszakats
changed the title
WebSocket test 2305 fail and 2301 flaky on Windows (mingw-w64)
WebSocket test 2305 fail and 2301, 2302 flaky on Windows (mingw-w64)
May 18, 2024
vszakats
added a commit
that referenced
this issue
May 18, 2024
WebSockets: ``` TESTFAIL: These test cases failed: 2302 ``` Ref: https://github.com/curl/curl/actions/runs/9139155361/job/25131144383?pr=13689#step:14:9892 Follow-up to 36fd2dd #13599 Ref: #13692 Closes #13696
vszakats
changed the title
WebSocket test 2305 fail and 2301, 2302 flaky on Windows (mingw-w64)
WebSocket test 2305 permafail and 2301, 2302 flaky on Windows (mingw-w64)
May 20, 2024
vszakats
changed the title
WebSocket test 2305 permafail and 2301, 2302 flaky on Windows (mingw-w64)
WebSocket test 2305 permafail, 2301, 2302 flaky on Windows (mingw-w64)
May 20, 2024
vszakats
added a commit
to vszakats/curl
that referenced
this issue
May 20, 2024
Ref: curl#13692 Closes #xxxxx
vszakats
changed the title
WebSocket test 2305 permafail, 2301, 2302 flaky on Windows (mingw-w64)
WebSocket tests 2301, 2302 flaky on Windows (mingw-w64)
May 20, 2024
vszakats
referenced
this issue
May 27, 2024
MQTT / OmniOS: ``` TESTFAIL: These test cases failed: 1190 1198 3017 ``` Ref: https://github.com/curl/curl/actions/runs/9258522297/job/25468730731?pr=13694#step:3:10251 MQTT / OmniOS: ``` TESTFAIL: These test cases failed: 1194 2200 2203 2205 ``` Ref: https://github.com/curl/curl/actions/runs/9150523540/job/25155409832#step:3:10233 FTP / OmniOS: ``` TESTFAIL: These test cases failed: 1096 ``` Ref: https://github.com/curl/curl/actions/runs/9150702711/job/25155793948#step:3:10247 FTP / OmniOS: ``` TESTFAIL: These test cases failed: 381 ``` Ref: https://github.com/curl/curl/actions/runs/9163863822/job/25193897640#step:3:10230 FTP / OmniOS: ``` TESTFAIL: These test cases failed: 340 ``` Ref: https://github.com/curl/curl/actions/runs/9233804752/job/25406671742?pr=13771#step:3:10245 Ref: #13583 (comment)
This probably goes under the umbrella of a more generic problem where TFTP, WebSockets, MQTT and FTP are all kind of flaky in Windows CI machines. For now this has been mitigated by ignoring the results of most of these tests (except FTP). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the first time in CI I enabled WebSockets in a native Windows job with tests,
where
2305 fails consistently, 2301 and 2302 failed once each (so far):https://github.com/curl/curl/actions/runs/9133449443/job/25116951463#step:14:145022305: https://github.com/curl/curl/actions/runs/9133449443/job/25116951463#step:14:11075
2301: https://github.com/curl/curl/actions/runs/9133227792/job/25116241601#step:14:9886
2305: https://github.com/curl/curl/actions/runs/9133227792/job/25116241601#step:14:10002https://github.com/curl/curl/actions/runs/9134361774/job/25119734300#step:14:186162305: https://github.com/curl/curl/actions/runs/9134361774/job/25119734300#step:14:9896
2302: https://github.com/curl/curl/actions/runs/9139155361/job/25131144383?pr=13689#step:14:9892
Ref: #13599 (comment)
curl/libcurl version: master
operating system: Windows
Ref:
curl/.github/workflows/windows.yml
Line 147 in 36fd2dd
edit: test 2305 fixed via dbd626a #13724.
The text was updated successfully, but these errors were encountered: