Skip to content

Conversation

@taegyunkim
Copy link
Contributor

@taegyunkim taegyunkim commented Nov 3, 2025

Motivation

DD_PROFILING_STACK_V2_ENABLED is true since dd-trace-py v2.20.0, and the latest release is 3.18.0rc1

Changes

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • If PR title starts with [<language>], double-check that only <language> is impacted by the change
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added (or removed)?

@taegyunkim taegyunkim requested a review from a team as a code owner November 3, 2025 21:47
@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

CODEOWNERS have been resolved as:

utils/_context/_scenarios/profiling.py                                  @DataDog/system-tests-core

self.weblog_container.environment["LD_PRELOAD"] = (
"/opt/datadog/continuousprofiler/Datadog.Linux.ApiWrapper.x64.so"
)
elif library == "python":
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will it work for backport ? if no, a condition on library version must be added (ping me if you need help)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants