Repository navigation
Job summary and annotations in GitHub Actions and Azure Pipelines - #62
Merged
Merged
Conversation
A markdown results table (per device, failing flows with their first error, links to TestingBot) goes to $GITHUB_STEP_SUMMARY or the Azure build summary; each failure becomes an ::error / task.logissue annotation. Skipped with --json (stdout), for the artifacts command, and with TESTINGBOT_CI_SUMMARY=0.
Contributor
Author
|
Companion: testingbot/maestro-action#2 (sets |
jochen-testingbot
changed the base branch from
feat/maestro-cancel-previous
to
main
October 29, 2026 10:18
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.
Stacked on #61. CLI-only, no server change.
Results show up in the CI system's own UI instead of only in the log, for
maestro,espresso,xcuitestandstatus(newsrc/utils/ci_summary.ts, called fromfinishCommand):$GITHUB_STEP_SUMMARY: verdict, link to TestingBot, one row per device (flows passed / total for Maestro, result for Espresso/XCUITest, link to the run), then a Failures table with each failing flow's first error. Plus one::error title=TestingBot: <flow> on <device>::<error>\n<run url>annotation per failure (max 10 + a "N more" line, GitHub's per-step cap), properly escaped.$AGENT_TEMPDIRECTORYand attached with##vso[task.uploadsummary], failures as##vso[task.logissue type=error].latest), so a flow that passed on retry is not reported.--json(annotations are stdout commands, the summary file is still written); theartifactscommand (its run already published one);TESTINGBOT_CI_SUMMARY=0. Failures to write are logged at debug, never fail the command.cli.test.tsmocks it, so this repo's own CI does not write into its job summary.Heads-up, testingbot/maestro-action: it runs
@testingbot/cli@latestand writes its own summary, so after this CLI release action users would get two tables. It needsexport TESTINGBOT_CI_SUMMARY=0before the CLI call inscripts/run.sh(older CLIs ignore it), ideally merged before this release. That change is prepared but not pushed.Tests: markdown (Maestro with retried flow, Espresso), GitHub/Azure annotation escaping, publish paths (GitHub append,
--json, Azure, off/outside CI/no verdict, unwritable file). 857/857, lint + tsc clean. Not yet seen in a real Actions or Azure run.