Skip to content

ci(ci_visibility): increase parallelism for pytest suite [backport 2.5] #8173

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

Merged
merged 1 commit into from
Jan 23, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 23, 2024

Backport 8bb3dd8 from #8168 to 2.5.

The pytest tests added in #7833 increased the runtime for the pytest CircleCI suite.

This adds more parallelism to get the suite to execute faster.

https://app.circleci.com/pipelines/github/DataDog/dd-trace-py/54135/workflows/7e4c17d1-e66c-466d-913b-06b70ddb4415/jobs/3447481 shows 4x parallelism , and the job completing in ~10 minutes which is bringing it back to a more reasonable timeframe.

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.
  • If change touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.

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

The `pytest` tests added in #7833 increased the runtime for the pytest
CircleCI suite.

This adds more parallelism to get the suite to execute faster.

https://app.circleci.com/pipelines/github/DataDog/dd-trace-py/54135/workflows/7e4c17d1-e66c-466d-913b-06b70ddb4415/jobs/3447481
shows 4x parallelism , and the job completing in ~10 minutes which is
bringing it back to a more reasonable timeframe.

## Checklist

- [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] If change touches code that signs or publishes builds or packages,
or handles credentials of any kind, I've requested a review from
`@DataDog/security-design-and-guidance`.

## Reviewer Checklist

- [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 8bb3dd8)
@github-actions github-actions bot requested a review from a team as a code owner January 23, 2024 07:54
@github-actions github-actions bot added the changelog/no-changelog A changelog entry is not required for this PR. label Jan 23, 2024
@romainkomorn-exdatadog romainkomorn-exdatadog enabled auto-merge (squash) January 23, 2024 08:57
@pr-commenter
Copy link

pr-commenter bot commented Jan 23, 2024

Benchmarks

Benchmark execution time: 2024-01-23 08:58:19

Comparing candidate commit d1af700 in PR branch backport-8168-to-2.5 with baseline commit cc67127 in branch 2.5.

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

scenario:span-add-metrics

  • 🟥 max_rss_usage [+21.879MB; +21.992MB] or [+53.889%; +54.167%]

auto-merge was automatically disabled January 23, 2024 08:59

Pull request was closed

@romainkomorn-exdatadog romainkomorn-exdatadog enabled auto-merge (squash) January 23, 2024 09:05
auto-merge was automatically disabled January 23, 2024 14:24

Pull request was closed

@romainkomorn-exdatadog romainkomorn-exdatadog deleted the backport-8168-to-2.5 branch January 23, 2024 14:35
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants