-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
runtests: add option -u to error on server unexpectedly alive #7180
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
3 times, most recently
from
July 19, 2021 10:06
a6930d0
to
f2e60fd
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
July 22, 2021 10:45
f2e60fd
to
e37e3ad
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
July 23, 2021 18:54
e37e3ad
to
a854a9a
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
July 25, 2021 18:04
a854a9a
to
cd993f6
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
July 29, 2021 06:13
cd993f6
to
85daa74
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
August 15, 2021 10:12
85daa74
to
a3ff01c
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
August 17, 2021 19:46
a3ff01c
to
389edbb
Compare
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
August 19, 2021 10:28
389edbb
to
3b3799a
Compare
bagder
requested changes
Aug 19, 2021
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.
The commit message needs an update. I suppose the reason for this option is to detect and provide a way to debug problems with killing off test servers?
Let's try to actually handle the server unexpectedly alive case by first making them visible on CI builds as failures. This is needed to detect issues with killing of the test servers completely including nested process chains with multiple PIDs per test server (including bash and perl). On Windows/cygwin platforms this is especially helpful with debugging PID mixups due to cygwin using its own PID space. Reviewed-by: Daniel Stenberg Closes curl#7180
mback2k
force-pushed
the
fail-unexpected-testserver-alive
branch
from
August 20, 2021 10:58
3b3799a
to
60a6d1d
Compare
Thanks for the feedback @bagder. I just rebased and pushed an extended commit message. |
bagder
approved these changes
Sep 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's try to actually handle the server unexpectedly alive
case by first making them visible on CI builds as failures.