Ensure that _dd.srv_src is inherited

[amarziali]

Motivation

Add a parametric test to ensure that, when a child span is opened without setting any service name, it inherits the service source from the parent

I also simplified the manifest and marked as a bug (with the related jira) for dotnet

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

• Anything but tests/ or manifests/ is modified ? 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, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

manifests/cpp.yml                                                       @DataDog/dd-trace-cpp
manifests/cpp_httpd.yml                                                 @DataDog/dd-trace-cpp
manifests/cpp_nginx.yml                                                 @DataDog/dd-trace-cpp
manifests/dotnet.yml                                                    @DataDog/apm-dotnet @DataDog/asm-dotnet
manifests/golang.yml                                                    @DataDog/dd-trace-go-guild
manifests/java_otel.yml                                                 @DataDog/system-tests-core
manifests/nodejs.yml                                                    @DataDog/dd-trace-js
manifests/nodejs_otel.yml                                               @DataDog/system-tests-core
manifests/php.yml                                                       @DataDog/apm-php @DataDog/asm-php
manifests/python.yml                                                    @DataDog/apm-python @DataDog/asm-python
manifests/python_lambda.yml                                             @DataDog/apm-python @DataDog/asm-python
manifests/python_otel.yml                                               @DataDog/apm-python @DataDog/asm-python
manifests/ruby.yml                                                      @DataDog/ruby-guild @DataDog/asm-ruby
manifests/rust.yml                                                      @DataDog/apm-rust
tests/parametric/test_tracer.py                                         @DataDog/system-tests-core @DataDog/apm-sdk-capabilities

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0deeae24c3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add manifest gating for new service-source inheritance test

This new parametric test is introduced without corresponding manifest declarations, so it will run by default on every library/version, including ones where this feature is explicitly marked unsupported for sibling tests in the same class (for example manifests/python.yml:1800-1801, manifests/nodejs.yml:2130-2131, manifests/ruby.yml:1557-1558, manifests/cpp.yml:290-291). In this repo, manifest rules control activation/deactivation at collection time (conftest.py::pytest_collection_modifyitems), so missing entries here can cause broad CI regressions outside Java/.NET/Golang support windows.

Useful? React with 👍 / 👎.

[datadog-prod-us1-4]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 003d0b7 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}

[pabloerhard]

Wasn't this behavior something we only wanted for tracers in which spans inherit service name from their parent spans?

[amarziali]

Wasn't this behavior something we only wanted for tracers in which spans inherit service name from their parent spans?

no worries, in this case, like for other tests, we can use irrelevant to exclude specific tracers (like node) from running this test. But it's still valuable to keep it enforced cross tracer for the ones that have this feature