Repository navigation
Conversation
angular-robot
Bot
added
the
area: build & ci
atscott
force-pushed
the
ci-failure-annotations
branch
2 times, most recently
from
November 11, 2026 03:06
c4d70e8 to
dfdb2aa
Compare
Run the test, build, and lint steps of `.github/workflows/ci.yml` through `scripts/ci/run-with-annotations.mts` so failed steps emit a GitHub Actions `::error` workflow command. This surfaces the failure cause directly in the GitHub Actions run summary and through the public Check Runs Annotations API, making it possible for developers, triage tools, and CI dashboards to determine what failed without downloading or scanning multi-megabyte job log archives (or requiring authenticated log downloads). For Bazel test and build steps, the annotation lists the targets that failed or timed out along with their test output excerpts and compiler diagnostics for build failures, while excluding flaky targets that passed on a retry. For other steps, it includes the tail of the command output. Nothing is emitted when a run is cancelled (such as when a newer commit supersedes a branch build).
atscott
force-pushed
the
ci-failure-annotations
branch
from
November 11, 2026 19:50
d83a3df to
aa2c3c9
Compare
atscott
marked this pull request as ready for review
November 11, 2026 20:03
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.
Run the test, build, and lint steps of
.github/workflows/ci.ymlthrough
scripts/ci/run-with-annotations.mtsso failed steps emit aGitHub Actions
::errorworkflow command.This surfaces the failure cause directly in the GitHub Actions run
summary and through the public Check Runs Annotations API, making it
possible for developers, triage tools, and CI dashboards to determine what
failed without downloading or scanning multi-megabyte job log archives
(or requiring authenticated log downloads).
For Bazel test and build steps, the annotation lists the targets that
failed or timed out along with their test output excerpts and compiler
diagnostics for build failures, while excluding flaky targets that passed
on a retry. For other steps, it includes the tail of the command output.
Nothing is emitted when a run is cancelled (such as when a newer commit
supersedes a branch build).