Skip to content

Conversation

@github-actions
Copy link
Contributor

Backport 36dcd9f from #12855 to 3.3.

the test_load_testing_appsec_1click_and_ip_blocking_gunicorn_block_and_kill_child_worker test has this decorator:

@flaky(until=1742580778, reason="_request_403 is flaky, figure out the error")

and its failing today because time() > 1742580778

We need to investigate that error. Removing flaky, updating to skip and link this problem to task APPSEC-57052

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

the
`test_load_testing_appsec_1click_and_ip_blocking_gunicorn_block_and_kill_child_worker`
test has this decorator:
```
@flaky(until=1742580778, reason="_request_403 is flaky, figure out the error")
```

and its failing today because `time() > 1742580778`

We need to investigate that error. Removing `flaky`, updating to `skip`
and link this problem to task APPSEC-57052

## 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 36dcd9f)
@github-actions github-actions bot requested a review from a team as a code owner March 24, 2025 18:09
@github-actions github-actions bot added changelog/no-changelog A changelog entry is not required for this PR. ASM Application Security Monitoring labels Mar 24, 2025
@erikayasuda erikayasuda merged commit 7989724 into 3.3 Mar 24, 2025
1 of 5 checks passed
@erikayasuda erikayasuda deleted the backport-12855-to-3.3 branch March 24, 2025 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ASM Application Security Monitoring 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