roachtest: use title override for schema change workload failures#169578
Merged
trunk-io[bot] merged 1 commit intocockroachdb:masterfrom May 4, 2026
Merged
roachtest: use title override for schema change workload failures#169578trunk-io[bot] merged 1 commit intocockroachdb:masterfrom
trunk-io[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
Schema change workload failures in DR roachtests (backup-restore,
c2c) are rerouted to sql-foundations via ErrorWithOwner. However,
since issue deduplication is title-based, a subsequent non-schema-change
failure would match the existing sql-foundations issue instead of
creating a new one for disaster-recovery.
Add a TitleOverride so schema change workload failures get a distinct
issue title ("schema_change_workload_failure"), preventing dedup
collisions with real DR test failures.
Epic: none
Release note: None
Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
Contributor
|
😎 Merged successfully - details. |
Member
Collaborator
Author
|
TFTR! /trunk merge |
|
Detected infrastructure failure on trunk-merge branch (matched: self-hosted runner lost communication with the server). Automatically resubmitting to merge queue (attempt 1 of 2). (run link) |
|
/trunk merge |
This was referenced May 4, 2026
|
Encountered an error creating backports. Some common things that can go wrong:
You might need to create your backport manually using the backport tool. merge conflict cherry-picking 35f4fd1 to blathers/backport-release-24.3-169578 Backport to branch release-24.3 failed. See errors above. merge conflict cherry-picking 35f4fd1 to blathers/backport-release-25.2-169578 Backport to branch release-25.2 failed. See errors above. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Schema change workload failures in DR roachtests (backup-restore,
c2c) are rerouted to sql-foundations via ErrorWithOwner. However,
since issue deduplication is title-based, a subsequent non-schema-change
failure would match the existing sql-foundations issue instead of
creating a new one for disaster-recovery.
Add a TitleOverride so schema change workload failures get a distinct
issue title ("schema_change_workload_failure"), preventing dedup
collisions with real DR test failures.
Epic: none
Release note: None