Repository navigation
Give the CI check job enough time for fleet integration - #48
Merged
Merged
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
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.
The
checkjob reaches the new two-node fleet integration test almost 10 minutes after starting, then GitHub cancels it at the existing 10-minute job deadline. Main run https://github.com/sidequery/artifacts/actions/runs/38411516264 passed every preceding step but was cancelled 24 seconds into the fleet test, preventing image publication.Increase the job deadline to 20 minutes. Individual test timeouts remain unchanged. This is a one-line workflow change; the diff was inspected and
git diff --checkpassed.This unblocks publishing the runtime and fleet publisher images needed by https://github.com/atm-com/kubernetes-manifests/pull/454. Rerunning the old run alone cannot apply the new workflow timeout.