Re-run erred task on ComputeTaskEvent#7967
Merged
crusaderky merged 2 commits intodask:mainfrom Jul 7, 2023
Merged
Conversation
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 20 files + 1 20 suites +1 11h 41m 50s ⏱️ + 1h 12m 30s For more details on these failures, see this check. Results for commit 7d9c748. ± Comparison against base commit 67e073f. |
2 tasks
crusaderky
approved these changes
Jul 7, 2023
Collaborator
|
I agree this use case should never happen. |
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.
Addresses #7933 (comment)
I'm not sure if this condition can ever occur, but it still makes sense to harden the state machine against it and add a test.
pre-commit run --all-files