-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable test retry for daily builds #13086
Conversation
@@ -10,19 +10,16 @@ jobs: | |||
common: | |||
uses: ./.github/workflows/build-common.yml | |||
with: | |||
max-test-retries: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would think if we wanted to enable retries we would need to increase this value instead of remove it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See
opentelemetry-java-instrumentation/conventions/src/main/kotlin/otel.java-conventions.gradle.kts
Lines 369 to 370 in edbd9aa
val defaultMaxRetries = if (System.getenv().containsKey("CI")) 5 else 0 | |
val maxTestRetries = gradle.startParameter.projectProperties["maxTestRetries"]?.toInt() ?: defaultMaxRetries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for pointing that out
.github/workflows/build-common.yml
Outdated
@@ -290,6 +290,25 @@ jobs: | |||
if: ${{ !cancelled() && hashFiles('build-scan.txt') != '' }} | |||
run: cat build-scan.txt | |||
|
|||
- name: Get current job url | |||
uses: Tiryoh/gha-jobid-action@be260d8673c9211a84cdcf37794ebd654ba81eef # v1.4.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have security worries about using unpopular external actions, is there another way? would it be ok to just link to the run? https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replaced that action with a different solution that uses actions/github-script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
and collect info about flaky tests into a google sheet.