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: set the default of _should_skip to false #11274

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

wantsui
Copy link
Collaborator

@wantsui wantsui commented Nov 1, 2024

While reviewing the flaky marker in gunicorn's test_span_schematization in

@flaky(until=1706677200)
, @brettlangdon pointed out that the timestamp is long past.

ie:

@flaky(until=1706677200)

This translates to Jan 31, 2024.

However, if you run the test for test_span_schematization today, it passes fine because it is getting skipped:

1 passed with 0 warnings, 0 failed

The bug fix here is to set the default to false, but keep the spirit of the original condition if statement.

If you rerun the test_span_schematization with this branch, it now doesn't get skip and the test correctly fails:

FAILED tests/contrib/gunicorn/test_gunicorn.py::test_span_schematization - AttributeError: module 'ddtrace.internal.compat' has no attribute 'stringify'

Leaving this PR in a draft state for now to see what other tests this affects.

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

Copy link
Contributor

github-actions bot commented Nov 1, 2024

CODEOWNERS have been resolved as:

tests/utils.py                                                          @DataDog/python-guild

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

datadog-dd-trace-py-rkomorn bot commented Nov 1, 2024

Datadog Report

Branch report: wantsui/fix-should-skip
Commit report: 697b076
Test service: dd-trace-py

✅ 0 Failed, 1048 Passed, 550 Skipped, 17m 53.28s Total duration (23m 8.72s time saved)

tests/utils.py Outdated Show resolved Hide resolved
@wantsui wantsui changed the title fix: set the default of _should_skip to false chore: set the default of _should_skip to false Nov 1, 2024
@pr-commenter
Copy link

pr-commenter bot commented Nov 8, 2024

Benchmarks

Benchmark execution time: 2025-02-10 19:27:53

Comparing candidate commit ba6c4cd in PR branch wantsui/fix-should-skip with baseline commit 848c921 in branch main.

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

@wantsui wantsui added the changelog/no-changelog A changelog entry is not required for this PR. label Nov 14, 2024
avara1986 pushed a commit that referenced this pull request Nov 15, 2024
As part of #11274, the
previous `until` timestamp for grpc was Oct 2024 which has already
passed. Unless anyone knows about ipv6 support, this PR extends the
timestamp until Jan 2025 to buy some more time.

## 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)
tests/utils.py Outdated Show resolved Hide resolved
wantsui added a commit that referenced this pull request Nov 20, 2024
The pyramid test flaky marker was set to Jan 2024 so it is expired by
now. This PR updates the test.

While looking at the failed pipelines, example:
https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-py/-/jobs/703862626

One of the reasons it fails is because there's a new base service name
and it is no longer blank:
```
meta mismatch on '_dd.base_service': got 'tests.contrib.pyramid.app' which does not match expected ''.
```
Related to #11274

Also, this PR sets a new flaky timestamp because the pyramid sample app
doesn't spin up correctly in the subprocesses, leading to failed tests.

Relates to AIDM-483

## 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)
emmettbutler pushed a commit that referenced this pull request Dec 19, 2024
The `until` timestamp in the flaky decorator on Django snapshots has
been expired since Jan 2024, which was uncovered by
#11274

As seen in this failed run:
https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-py/-/jobs/742978251,
if we remove it, the current failure is on:
> meta mismatch on '_dd.base_service': got 'tests.contrib.django' which
does not match expected ''.


## 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)
@wantsui wantsui force-pushed the wantsui/fix-should-skip branch from 697b076 to 8c5208a Compare February 7, 2025 15:55
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented Feb 7, 2025

Datadog Report

Branch report: wantsui/fix-should-skip
Commit report: ba6c4cd
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1184 Skipped, 3m 24.99s Total duration (25m 54.8s time saved)

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