[PROF-12799] Fix python crashtracker smoke test #5585
Draft
+15
−1
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
Related to this https://datadoghq.atlassian.net/browse/INPLAT-603
Changes
/crashmeendpoints for node and python test app. This is because, when debugging the test that fails in CI locally in workspaces, I noticed that the test behavior was different depending on whether I ran the failing test as part of thedefaultscenario, or the specificdocker_ssi_crashtrackingscenario. The test seemed to fail when run all together, but when run specifically within its scenario, it would pass. I updated the test setup code to simply use Weblog for whatever scenario env it is currently in.Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
[<language>], double-check that only<language>is impacted by the changebuild-XXX-imagelabel is present