Skip to content
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

ci: add macrobenchmarks retry option [backport 2.8] #9573

Merged
merged 2 commits into from
Jun 18, 2024
Merged

Conversation

gnufede
Copy link
Member

@gnufede gnufede commented Jun 18, 2024

CI: adds option to retry the macrobenchmarks, useful since we can fail to allocate all the required machines for running the different scenarios at once

Checklist

  • Change(s) are motivated and described in the PR description
  • Testing strategy is described if automated tests are not included in the PR
  • Risks are described (performance impact, potential for breakage, maintainability)
  • Change is maintainable (easy to change, telemetry, documentation)
  • Library release note guidelines are followed or label changelog/no-changelog is set
  • Documentation is included (in-code, generated user docs, public corp docs)
  • Backport labels are set (if applicable)
  • If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Description motivates each change
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Change is maintainable (easy to change, telemetry, documentation)
  • Release note makes sense to a user of the library
  • Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance
    policy

(cherry picked from commit 30f6413)

CI: adds option to retry the macrobenchmarks, useful since we can fail
to allocate all the required machines for running the different
scenarios at once

- [x] Change(s) are motivated and described in the PR description
- [x] Testing strategy is described if automated tests are not included
in the PR
- [x] Risks are described (performance impact, potential for breakage,
maintainability)
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed or label `changelog/no-changelog` is set
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/))
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
- [x] If this PR changes the public interface, I've notified
`@DataDog/apm-tees`.

- [x] Title is accurate
- [x] All changes are related to the pull request's stated goal
- [x] Description motivates each change
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- [x] Testing strategy adequately addresses listed risks
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] Release note makes sense to a user of the library
- [x] Author has acknowledged and discussed the performance implications
of this PR as reported in the benchmarks PR comment
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit 30f6413)
@gnufede gnufede marked this pull request as ready for review June 18, 2024 08:30
@gnufede gnufede requested a review from a team as a code owner June 18, 2024 08:30
@gnufede gnufede requested a review from erikayasuda June 18, 2024 08:30
@gnufede gnufede added changelog/no-changelog A changelog entry is not required for this PR. CI labels Jun 18, 2024
@gnufede gnufede enabled auto-merge (squash) June 18, 2024 08:55
@pr-commenter
Copy link

pr-commenter bot commented Jun 18, 2024

Benchmarks

Benchmark execution time: 2024-06-18 09:33:25

Comparing candidate commit 3ce0b8b in PR branch backport-9567-to-2.8 with baseline commit 1177df2 in branch 2.8.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 193 metrics, 9 unstable metrics.

@gnufede gnufede merged commit 6fa908e into 2.8 Jun 18, 2024
68 of 77 checks passed
@gnufede gnufede deleted the backport-9567-to-2.8 branch June 18, 2024 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR. CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants