When a bors merge attempt fails, bors posts a message "Build failed" with a link to teamcity.
That message could be made to look more like a test failure report, which tries to mention the failed test(s) and/or the stack trace, if something crashed (for example #25203).
This would save devs a lot of time triaging these themselves. Often, bors merge failures are due to flaky tests since they are usually preceded by a green run on the branch, and merge conflicts are relatively rare.
Epic DEVINF-228
Jira issue: CRDB-5700
When a bors merge attempt fails, bors posts a message "Build failed" with a link to teamcity.
That message could be made to look more like a test failure report, which tries to mention the failed test(s) and/or the stack trace, if something crashed (for example #25203).
This would save devs a lot of time triaging these themselves. Often, bors merge failures are due to flaky tests since they are usually preceded by a green run on the branch, and merge conflicts are relatively rare.
Epic DEVINF-228
Jira issue: CRDB-5700