chore(tools/v2fix): upgrade dd-trace-go.v1 to avoid v2 non-compatible warning#3814
Conversation
BenchmarksBenchmark execution time: 2025-07-30 08:41:17 Comparing candidate commit 3979a1c in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit c639002: What to do next?
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit 3df1ce7: What to do next?
|
|
Personal note: Don't forget to |
12ab454 to
3979a1c
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
What does this PR do?
Closes #3791 #3804 by upgrading the v1 tracer, as the customer did in #3804. The reason to not adopt the customer's PR is because they are introducing multiple changes regarding Go versions and libraries that are not related to upgrading the v1 tracer.
Motivation
The warning that the customer reports in #3791 is because both tracer versions - v1 and v2 - are bundled into v2fix due to the way it was designed. It's not a blocking warning, as it has no impact in v2fix checks.
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!