[DEBUG] Azure DevOps Windows CI flakiness #5904
Closed
Conversation
This file contains hidden or 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
141c7e3 to
d86d6b9
Compare
|
Waiting for the issue described in PR #5954 to be fixed before going further with this. |
d86d6b9 to
10da11e
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Interesting... I am unable to make the Azure DevOps builds fail in this PR. Let's try again. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
d535228 to
e5f4e4c
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
First: remove all other CI to avoud using their resources.
46cfd26 to
a273282
Compare
Second: patch ltmain.sh to use job group for child process Make sure child processes are killed if lt-wrapper is killed.
a273282 to
16a5236
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mback2k
added a commit
to mback2k/curl
that referenced
this pull request
Oct 7, 2020
Install curl binaries into MinGW bin folder and use that for the tests in order to avoid libtool wrapper binaries. The libtool wrapper binaries (not scripts) on Windows seem to be the root cause of the following issues: 1. Process output can be lost in the wrapper process chain. 2. Killing the wrapper process does not kill the real one. Derived from curl#5904
mback2k
added a commit
to mback2k/curl
that referenced
this pull request
Oct 15, 2020
Install curl binaries into MinGW bin folder and use that for the tests in order to avoid libtool wrapper binaries. The libtool wrapper binaries (not scripts) on Windows seem to be one of the root causes for the following issues: 1. Process output can be lost in the wrapper process chain. 2. Killing the wrapper process does not kill the real one. Derived from curl#5904 Closes curl#6049
mback2k
added a commit
that referenced
this pull request
Oct 16, 2020
Install curl binaries into MinGW bin folder and use that for the tests in order to avoid libtool wrapper binaries. The libtool wrapper binaries (not scripts) on Windows seem to be one of the possible causes for the following issues: 1. Process output can be lost in the wrapper process chain. 2. Killing the wrapper process does not kill the actual one. Derived from #5904 Closes #6049
|
Not using this PR anymore, closing.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Please do not merge this. This PR is just a placeholder to perform debugging of the Windows CI flakiness on Azure DevOps.
This PR will be force-pushed and turn apart multiple times...