-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
tests: frequent failure of test 2600 on Windows #14177
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
Comments
|
One trend seems interesting: Cygwin and MSYS builds running on the same runner seem stable. Native Windows ones: odd hangs and flakiness. I have no clue why that is. Possibly Windows is just like that, but then why Cygwin and MSYS run fine? Cygwin running with |
I think we should disable this test for Windows. It uses the file descriptor |
- disbable this test on WIN32 platforms. It uses the file describtor '1' as valid socket without events. Not portable. - reduce trace output somewhat on other runs - refs curl#14177
#14191 as proposed fix. |
- disbable this test on WIN32 platforms. It uses the file describtor '1' as valid socket without events. Not portable. - reduce trace output somewhat on other runs Fixes curl#14177 Reported-by: Viktor Szakats Closes curl#14191
I did this
Started seeing lots
unit2600
failures recently (in the last week or so). Thiscan be been related to disabling more test groups and thus giving way to
this one, so it's not necessarly a recent regression.
This is often the last reported test, before the jobs hanging and timing out.
It happened with various mingw and MSVC configurations and versions.
Example:
Ref: https://github.com/curl/curl/actions/runs/9919874100/job/27406166474?pr=14175#step:13:5436
A collection of similar failures:
via #13599 (comment)
I expected the following
Test to finish, ideally with success.
curl/libcurl version
master (8.9.0-DEV)
operating system
Windows
The text was updated successfully, but these errors were encountered: