test(debugger): stabilize code origin enablement #6160
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Motivation
CI intermittently fails
tests/debugger/test_debugger_inproduct_enablement.py::Test_Debugger_InProduct_Enablement_Code_Origin::test_inproduct_enablement_code_originonnodejs/fastifywithAssertionError: Expected code origin enabled by default(example). The failure is flaky (rerun passes), which points to a timing window in how we detect code origin spans rather than a deterministic tracer behavior change.Changes
tests/debugger/utils.py.tests/debugger/test_debugger_inproduct_enablement.pyto pass the request/response into the waiter so the check is tied to the exact/request under test.This should avoid a race where the relevant
/api/v0.2/tracespayload is ingested before the previous threshold-based wait begins scanning, producing a false negative under CI timing.Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present