chore(ci): retry flaky tasks #3697
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
No code generatedIf you believe code should've been generated, please, report the issue. 📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
millotp
commented
Sep 12, 2024
| @@ -430,13 +430,14 @@ jobs: | |||
| type: minimal | |||
| language: kotlin | |||
|
|
|||
| - name: remove previous build from linux | |||
shortcuts
reviewed
Sep 16, 2024
| @@ -622,7 +630,7 @@ jobs: | |||
|
|
|||
| push_and_release: | |||
| runs-on: ubuntu-22.04 | |||
| timeout-minutes: 15 | |||
| timeout-minutes: 30 | |||
There was a problem hiding this comment.
kotlin is taking 12 min to deploy and often fails, so weed need 30 min when it retries
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.
🧭 What and Why
Some jobs on the CI fails a lot, for different reasons, we can add a bit of retry for the 2 macOS jobs, and for the release because maven is often down, or kotlin has a weird failure.