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
@vivek-datadog noticed that the "Upload Traces" workflow in CI was taking half to two-thirds of the total test time, on master test runs. Optimizing that part is definitely a low-hanging fruit!
What does this PR do?
This PR speeds up the "trace upload" workflow so that it runs in 2 minutes instead of 50 minutes, for the master test runs. The total test time was 1.5 - 2 hours before this change.
A large amount of logging was slowing down the GitHub actions job.
The agent log level is now set to "warn" instead of "trace". Also, only the test name and the HTTP status code are now printed, instead of the full response from the Agent:
Example fast trace upload (with the changes in this PR): https://github.com/DataDog/integrations-core/actions/runs/11895100489/job/33147224198?pr=19078
Example slow speed (without the changes in this PR): https://github.com/DataDog/integrations-core/actions/runs/11862839027/job/33064564080
This PR probably won't have a big impact on PR test runs (unless a lot of integrations are modified).
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged