Skip to content

release-26.1: roachtest: refactor datadog upload flags#162607

Merged
github-actions[bot] merged 1 commit intocockroachdb:release-26.1from
williamchoe3:blathers/backport-release-26.1-162558
Feb 7, 2026
Merged

release-26.1: roachtest: refactor datadog upload flags#162607
github-actions[bot] merged 1 commit intocockroachdb:release-26.1from
williamchoe3:blathers/backport-release-26.1-162558

Conversation

@williamchoe3
Copy link
Copy Markdown
Contributor

@williamchoe3 williamchoe3 commented Feb 6, 2026

Backport 1/1 commits from #162558 on behalf of @williamchoe3.


Previously, all test.log logs would be uploaded regardless of result status.
Now test logs will only be uploaded for failed tests to help reduce overall volume.
Added a flag to enable upload regardless of result --datadog-send-logs-any-result. Also renamed --datadog-always-upload to --datadog-send-logs-any-branch to avoid confusion with the new flag


Release justification: Test observability only change

Previously, all test.log logs would be uploaded regardless of result status.
Now test logs will only be uploaded for failed tests to help reduce overall
volume. Added a flag to enable upload regardless of result
--datadog-send-logs-any-result. Also renamed --datadog-always-upload to
--datadog-send-logs-any-branch to avoid confusion with the new flag

Epic: None
Release note: None
@williamchoe3 williamchoe3 requested a review from a team as a code owner February 6, 2026 18:59
@blathers-crl blathers-crl Bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Feb 6, 2026
@williamchoe3 williamchoe3 removed the request for review from a team February 6, 2026 18:59
@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented Feb 6, 2026

Thanks for opening a backport.

Before merging, please confirm that the change does not break backwards compatibility and otherwise complies with the backport policy. Include a brief release justification in the PR description explaining why the backport is appropriate. All backports must be reviewed by the TL for the owning area. While the stricter LTS policy does not yet apply, please exercise judgment and consider gating non-critical changes behind a disabled-by-default feature flag when appropriate.

@blathers-crl blathers-crl Bot added backport Label PR's that are backports to older release branches T-testeng TestEng Team labels Feb 6, 2026
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@blathers-crl blathers-crl Bot added the backport-test-only Used to denote the backport has only non-production changes label Feb 6, 2026
@github-actions github-actions Bot merged commit 29869de into cockroachdb:release-26.1 Feb 7, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches backport-test-only Used to denote the backport has only non-production changes blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. T-testeng TestEng Team v26.1.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants