Repository navigation
Conversation
Alternative approach on narrowing down the subprocess failures. Assumption is that no timeout will occour if all tests are run sequentially.
Change to rerun CI
Member
Author
|
First run was ok. Triggering a second one. |
Member
Author
|
Second run was ok. Triggering a third one. |
timhoffm
marked this pull request as draft
April 29, 2025 12:43
Member
Author
|
I count three passed CI runs in a row as confirmation of the assumtion:
|
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
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.
Alternative approach on narrowing down the subprocess failures. Assumption is that no timeout will occour if all tests are run sequentially.
See #29797 (comment)
Note: This is not intended to be merged. It's only a test PR to narrow down the issue and confirm above assumption.