Increase Go test coverage run timeout to 25 minutes #33223
Merged
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
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment |
damccorm
reviewed
Nov 26, 2024
.github/workflows/go_tests.yml
Outdated
| @@ -50,6 +50,7 @@ jobs: | |||
| - name: Delete old coverage | |||
| run: "cd sdks && rm -rf .coverage.txt || :" | |||
| - name: Run coverage | |||
| timeout-minutes: 25 | |||
There was a problem hiding this comment.
There is no default step timeout, so I don't think this does what you're expecting. I assume the mentioned timeout was for an individual test or the command itself
There was a problem hiding this comment.
The timeout is the default 'go test' timeout, so a flag needs to be added to the go test call down below in the run clause.
-timeout=25m
damccorm
requested changes
Nov 26, 2024
lostluck
requested changes
Nov 26, 2024
.github/workflows/go_tests.yml
Outdated
| @@ -50,6 +50,7 @@ jobs: | |||
| - name: Delete old coverage | |||
| run: "cd sdks && rm -rf .coverage.txt || :" | |||
| - name: Run coverage | |||
| timeout-minutes: 25 | |||
There was a problem hiding this comment.
The timeout is the default 'go test' timeout, so a flag needs to be added to the go test call down below in the run clause.
-timeout=25m
kennknowles
force-pushed
the
go-coverage-timeout
branch
from
856e92a to
e1b7b3f
Compare
|
PTAL |
lostluck
approved these changes
Nov 26, 2024
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.
This may at least partially address #32627. Following the suggestion by @lostluck there.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.