roachtest: print issue number after test failure#118914
Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom Feb 8, 2024
Merged
roachtest: print issue number after test failure#118914craig[bot] merged 1 commit intocockroachdb:masterfrom
craig[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
Member
|
This change is |
b2d6ea8 to
86765b5
Compare
Author
srosenberg
approved these changes
Feb 8, 2024
86765b5 to
12aaa9e
Compare
This commit updates the GitHub issue poster so that information about the issue is returned when an issue is created or a comment added. The roachtest test runner uses this information in the TeamCity output so that we can easily see the issue corresponding to a test failure directly in the TC overview page. Epic: none Release note: None
12aaa9e to
fa69450
Compare
Author
|
TFTR! bors r=srosenberg |
Contributor
|
Build succeeded: |
|
Encountered an error creating backports. Some common things that can go wrong:
You might need to create your backport manually using the backport tool. error creating merge commit from fa69450 to blathers/backport-release-23.1-118914: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict [] you may need to manually resolve merge conflicts with the backport tool. Backport to branch 23.1.x failed. See errors above. error creating merge commit from fa69450 to blathers/backport-release-23.2-118914: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict [] you may need to manually resolve merge conflicts with the backport tool. Backport to branch 23.2.x failed. See errors above. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
rickystewart
added a commit
to rickystewart/cockroach
that referenced
this pull request
Feb 9, 2024
This broke with cockroachdb#118914. Epic: CRDB-8308 Release note: None
This was referenced Feb 9, 2024
craig bot
pushed a commit
that referenced
this pull request
Feb 9, 2024
119019: process-bep-file: fix compile error r=rail a=rickystewart This broke with #118914. Epic: CRDB-8308 Release note: None 119026: build: add RC branches to release branches r=rickystewart a=rail Previously, we had logic to distinguish release and non-release branches (like customized builds) in the docker script. The pattern didn't cover cases, where we name the branches by adding the "-rc" suffix. This PR fixes the release branch pattern. Epic: none Release note: None Co-authored-by: Ricky Stewart <ricky@cockroachlabs.com> Co-authored-by: Rail Aliiev <rail@iqchoice.com>
renatolabs
pushed a commit
to renatolabs/cockroach
that referenced
this pull request
Feb 12, 2024
This broke with cockroachdb#118914. Epic: CRDB-8308 Release note: None
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
3 participants
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.
This commit updates the GitHub issue poster so that information about
the issue is returned when an issue is created or a comment
added. The roachtest test runner uses this information in the TeamCity
output so that we can easily see the issue corresponding to a test
failure directly in the TC overview page.
Epic: none
Release note: None