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(tracing): fix some service naming tests that were failing silently [backport 2.17] #11542

Merged
merged 2 commits into from
Nov 26, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Backport 81f52ca from #11483 to 2.17.

Motivation

See silent failures here.

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

…tly (#11483)

## Motivation

See silent failures
[here](https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-py/-/jobs/714753885#L6693).

DOES NOT NEED TO BE BACKPORTED, FIX WAS ALREADY INCLUDED IN EARLIER
BACKPORT PR

## 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
- [x] 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 81f52ca)
@github-actions github-actions bot requested a review from a team as a code owner November 25, 2024 22:48
@github-actions github-actions bot added changelog/no-changelog A changelog entry is not required for this PR. mergequeue-status: done labels Nov 25, 2024
@github-actions github-actions bot requested a review from a team as a code owner November 25, 2024 22:48
@wconti27 wconti27 self-assigned this Nov 25, 2024
@quinna-h quinna-h closed this Nov 25, 2024
@quinna-h quinna-h reopened this Nov 25, 2024
Copy link
Contributor Author

CODEOWNERS have been resolved as:

tests/contrib/botocore/test.py                                          @DataDog/apm-core-python @DataDog/apm-idm-python

@wconti27
Copy link
Contributor

/merge

@dd-devflow
Copy link

dd-devflow bot commented Nov 25, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-11-25 23:04:17 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-11-25 23:22:37 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in 2.17 is 0s.


2024-11-26 01:22:55 UTCMergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build took longer than expected. The current limit for the base branch '2.17' is 120 minutes.

Possible reasons:

  • target branch of PR is restricted to only allow up-to-date branches, but the pr is now outdated

@pr-commenter
Copy link

pr-commenter bot commented Nov 25, 2024

Benchmarks

Benchmark execution time: 2024-11-26 15:10:22

Comparing candidate commit f9a430e in PR branch backport-11483-to-2.17 with baseline commit f8fc03a in branch 2.17.

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

@wconti27 wconti27 enabled auto-merge (squash) November 26, 2024 15:06
@wconti27 wconti27 merged commit 5d48816 into 2.17 Nov 26, 2024
168 checks passed
@wconti27 wconti27 deleted the backport-11483-to-2.17 branch November 26, 2024 15:12
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. mergequeue-status: rejected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants