feat(python): add cpu-time gate scenarios for 3.14/3.15 migration - #164
Closed
vlad-scherbich wants to merge 8 commits into
Closed
feat(python): add cpu-time gate scenarios for 3.14/3.15 migration#164vlad-scherbich wants to merge 8 commits into
vlad-scherbich wants to merge 8 commits into
Conversation
dd-trace-js master dropped support for Node < 22 (supported runtimes are now >=22 <27). On node:18/node:20 base images the tracer aborts with "incompatible_runtime", so no profiles are written and the scenarios fail with "No matching files found for ...pprof". Bump all four node scenario base images to node:22-bullseye (active LTS, within the supported range). Verified locally: node_wall_cpu, node_heap_oom, and node_heap now produce profiles and pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bump node scenarios to node:22 for dd-trace-js compatibility
**What does this PR do?** This PR marks all Ruby heap-related tests as flaky, renaming the folders so they don't run by default in CI. **Motivation:** This PR attempts to "stop the bleeding" relating to the Ruby Heap tests being flaky: it's really annoying that these failures keep showing up in other prof-correctness where nothing changed for Ruby. I've started #154 to try to actually fix things, but until we have a good fix in place, let's avoid the annoyance to everyone else. **Additional Notes:** N/A **How to test the change?** Validate that `ruby_heap` tests are no longer running in CI (and CI is still green).
[Node.js] Add node allocations scenario
…am gate Add RE2-safe list-scenarios -exclude and ci.yml test_scenarios_exclude so wheel-only Python scenarios are not silently skipped. Ship Python 3.14/3.15 base images, dd-trace-py STS trigger policy, and a minimal migration gate index README; scenario workloads land in follow-up PRs.
…ync_gen) Add six paired scenarios for the migration gate with lock-release and lock name labels plus exception type labels. Stacks on gate-infra (PR-0).
Add paired python_cpu scenarios asserting stack cpu-time samples and thread-name labels on the migration gate path, growing coverage from 10 to 12 scenarios.
vlad-scherbich
force-pushed
the
vlad/python-cpu-gate-scenarios
branch
from
July 26, 2026 17:47
3b5725b to
f14a7ba
Compare
Contributor
Author
|
Closing in favor of #169 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Add paired python_cpu scenarios asserting stack cpu-time samples and thread-name labels on the migration gate path, growing coverage from 10 to 12 scenarios.