-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
tests: fix error handling around UNIX sockets #11265
Conversation
@gvanem Would you mind taking a look? |
818d6c1
to
9b48dea
Compare
@dfandrich No change. Same |
I'm not sure which versions of Windows is actually running on the CI services.
They might be running an older one that doesn't support UNIX sockets. In any
case, I'll submit this PR since the previous error checking was wrong.
|
9b48dea
to
d3136d8
Compare
d3136d8
to
b256eae
Compare
The wrong error code was checked on Windows on UNIX socket failures, which could have caused all UNIX sockets to be reported as having errored and the tests therefore skipped. Also, a useless error message was displayed on socket errors in many test servers on Windows because strerror() doesn't work on WinSock error codes; perror() is overridden there to work on all errors and is used instead. Ref #11258 Closes #11265
b256eae
to
0b5c51d
Compare
The wrong error code was checked on Windows on UNIX socket failures, which could have caused all UNIX sockets to be reported as having errored and the tests therefore skipped. Also, a useless error message was displayed on socket errors in many test servers on Windows because strerror() doesn't work on WinSock error codes; perror() is overridden there to work on all errors and is used instead. Ref #11258 Closes #11265
@@ -2779,6 +2779,7 @@ sub displaylogs { | |||
# a new one shortly. If all runners are busy, wait indefinitely for one to | |||
# finish. | |||
my $runnerwait = scalar(@runnersidle) && scalar(@runtests) ? 0 : undef; | |||
print STDERR "TESTING waiting indefinitely for test completion\n" if(!scalar(@runtests)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this print a debugging leftover or meant to actually be a plain STDERR output? It looks like an anomaly in the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a debugging leftover. It won't be submitted.
The wrong error code was checked on Windows on UNIX socket failures, which could have caused all UNIX sockets to be reported as having errored and the tests therefore skipped. Also, a useless error message was displayed on socket errors in many test servers on Windows because strerror() doesn't work on WinSock error codes; perror() is overridden there to work on all errors and is used instead. Ref curl#11258 Closes curl#11265
The wrong error code was checked on Windows on UNIX socket failures, which could have caused all UNIX sockets to be reported as having errored and the tests therefore skipped. Also, a useless error message was displayed on socket errors in many test servers on Windows because strerror() doesn't work on WinSock error codes; perror() is overridden there to work on all errors and is used instead. Ref curl#11258 Closes curl#11265
The wrong error code was checked on Windows, which may have caused all
UNIX sockets to be reported as error and the tests skipped.
Fixes #11258
Closes #11265