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(framework tests): skip failing sanic test [backport #6539 to 1.17] #6628

Merged
merged 4 commits into from
Aug 18, 2023

Conversation

P403n1x87
Copy link
Contributor

Backport of #6539 to 1.17

The sanic framework tests have recently started failing a single test: test_redirect_with_params, which has a weird error relating to string formatting: "sanic%20test" != "sanic test".
This test's assertion was subtly changed in the most recent release of sanic by altering the string formatting of the asserted string value, and this only started failing once the new version of sanic (23.3.0) was released, so we can consider skipping this test for now until we upgrade to match the latest version of sanic.

Checklist

  • Change(s) are motivated and described in the PR description.
  • Testing strategy is described if automated tests are not included in the PR.
  • Risk is outlined (performance impact, potential for breakage, maintainability, etc).
  • Change is maintainable (easy to change, telemetry, documentation).
  • Library release note guidelines are followed. If no release note is required, add label changelog/no-changelog.
  • Documentation is included (in-code, generated user docs, public corp docs).
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Title is accurate.
  • No unnecessary changes are introduced.
  • Description motivates each change.
  • Avoids breaking API changes unless absolutely necessary.
  • Testing strategy adequately addresses listed risk(s).
  • Change is maintainable (easy to change, telemetry, documentation).
  • Release note makes sense to a user of the library.
  • Reviewer has explicitly 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 sanic framework tests have recently started failing a single test:
`test_redirect_with_params`, which has a weird error relating to string
formatting: `"sanic%20test" != "sanic test"`.
This test's assertion was subtly changed in the most recent release of
sanic by altering the string formatting of the asserted string value,
and this only started failing once the new version of sanic (23.3.0) was
released, so we can consider skipping this test for now until we upgrade
to match the latest version of sanic.

- [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] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [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))

- [ ] Title is accurate.
- [ ] No unnecessary changes are introduced.
- [ ] Description motivates each change.
- [ ] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [ ] Testing strategy adequately addresses listed risk(s).
- [ ] Change is maintainable (easy to change, telemetry, documentation).
- [ ] Release note makes sense to a user of the library.
- [ ] Reviewer has explicitly 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 d06ec2f)
@P403n1x87 P403n1x87 requested a review from a team as a code owner August 10, 2023 11:01
@P403n1x87 P403n1x87 added changelog/no-changelog A changelog entry is not required for this PR. backport 1.16 labels Aug 10, 2023
@P403n1x87 P403n1x87 enabled auto-merge (squash) August 10, 2023 11:01
@pr-commenter
Copy link

pr-commenter bot commented Aug 10, 2023

Benchmarks

Benchmark execution time: 2023-08-15 17:09:18

Comparing candidate commit 71a981e in PR branch backport-6539-to-1.17 with baseline commit f393fc6 in branch 1.17.

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

@P403n1x87 P403n1x87 merged commit d387da5 into 1.17 Aug 18, 2023
24 checks passed
@P403n1x87 P403n1x87 deleted the backport-6539-to-1.17 branch August 18, 2023 11:20
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