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

chore(ci): remove lib-init image tests from this repo in favor of images built in system-tests [backport 2.14] #10832

Open
wants to merge 2 commits into
base: 2.14
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 26, 2024

Backport 9983895 from #10746 to 2.14.

This PR removes lib injection test images from this repo in favor of the ones in system-tests. The images in this repository were not used since the migration to one-pipeline. The transition from Github actions to Gitlab for kubernetes lib injection tests mean none of the injection tests in this repo ran.

With tests in both locations there is lots of potential for confusion.

To capture the changes that have been mistakenly applied to dd-trace-py images, there is a sister PR in system-tests: DataDog/system-tests#3089

Checklist

  • PR author has checked that all the criteria below are met
  • The PR description includes an overview of the change
  • The PR description articulates the motivation for the change
  • The change includes tests OR the PR description describes a testing strategy
  • The PR description notes risks associated with the change, if any
  • Newly-added code is easy to change
  • The change follows the library release note guidelines
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Reviewer has checked that all the criteria below are met
  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Newly-added code is easy to change
  • Release note makes sense to a user of the library
  • If necessary, 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

…ges built in system-tests (#10746)

This PR removes lib injection test images from this repo in favor of the
ones in `system-tests`. The images in this repository were not used
since the migration to `one-pipeline`. The transition from Github
actions to Gitlab for kubernetes lib injection tests mean none of the
injection tests in this repo ran.

With tests in both locations there is lots of potential for confusion.

To capture the changes that have been mistakenly applied to
`dd-trace-py` images, there is a sister PR in system-tests:
DataDog/system-tests#3089

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [ ] Reviewer has checked that all the criteria below are met
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, 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](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit 9983895)
@github-actions github-actions bot requested review from a team as code owners September 26, 2024 16:49
@github-actions github-actions bot added the changelog/no-changelog A changelog entry is not required for this PR. label Sep 26, 2024
@taegyunkim taegyunkim closed this Sep 26, 2024
@taegyunkim taegyunkim reopened this Sep 26, 2024
Copy link
Contributor Author

CODEOWNERS have been resolved as:

.gitlab-ci.yml                                                          @DataDog/apm-core-python
tests/.suitespec.json                                                   @DataDog/python-guild @DataDog/apm-core-python

@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented Sep 26, 2024

Datadog Report

Branch report: backport-10746-to-2.14
Commit report: 97b9499
Test service: dd-trace-py

✅ 0 Failed, 592 Passed, 694 Skipped, 18m 59.83s Total duration (18m 17.02s time saved)

@pr-commenter
Copy link

pr-commenter bot commented Sep 26, 2024

Benchmarks

Benchmark execution time: 2024-09-26 20:44:35

Comparing candidate commit 97b9499 in PR branch backport-10746-to-2.14 with baseline commit 467db5a in branch 2.14.

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

@randomanderson randomanderson enabled auto-merge (squash) September 26, 2024 17:59
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.

3 participants