bk job flaky-tests lists flaky tests for a failed job

Introduced 2026-10-08 · score 0.96

HOW TO USE IT

When inspecting a failed job for retry evidence, run `bk job flaky-tests <job-uuid>` to list failed tests Test Engine currently labels flaky. Treat an empty result as inconclusive; current labels do not establish why the job failed.

WHY THIS HELPS

When deciding whether to retry a failed job, inspect the failed tests Test Engine currently labels flaky.

REQUIREMENTS AND LIMITATIONS

• Version: v3.61.0
• <job-uuid> (required): UUID of the failed job to inspect.
• --text: Select text output.
• --json: Select JSON output; structured output includes job UUID, build UUID, test details, and execution metrics.
• --yaml: Select YAML output; structured output includes job UUID, build UUID, test details, and execution metrics.
• Prerequisite: Token requires `read_builds` and `read_suites` scopes.
• Prerequisite: Test Engine executions need the `build.job_id` tag matching the job UUID; missing or overridden collector job metadata may prevent matches.
• Requires `read_builds` and `read_suites` token scopes.
• Test Engine executions must be tagged with the matching `build.job_id`; missing or overridden collector job metadata can prevent matches.
• Current flaky labels do not prove flakiness caused the job failure.
• An empty result does not mean the tests are not flaky; Test Engine data may be missing or incomplete.
• The command fetches all pages.
• Live Test Engine data was not exercised.

FIRST-PARTY EVIDENCE

• https://github.com/buildkite/cli/releases/tag/v3.61.0
• https://github.com/buildkite/cli/pull/1021
• https://github.com/buildkite/cli/blob/v3.61.0/README.md
• https://github.com/buildkite/cli/blob/v3.61.0/cmd/job/flaky_tests.go

Check the installed version and the source before using it. Entry JSON

Report a problem with this card