Per-shard results from ci_nightly_pytorch_full_test.yml (6 default + 3 distributed + 2 inductor = 11 shards per run)
Loading…
Linux JAX Wheel Builds & Tests
Loading…
Legend
PASS Build SuccessfulFAIL Build FailedSKIPPED Test SkippedIN PROGRESS Currently RunningCANCELLED Build CancelledNO DATA No Recent RunsPENDING Not Started
Time format: Run time +Queue time
Release History
Last Updated: --
How to read this table.
Each row is one nightly ROCm version (newest first). Each workflow is one column showing passed/total.
Click any column header ▸ to expand it sideways into per-arch status dots; click an arch to drill into its full matrix.
The Downloads button opens a popover with TAR / DEB / RPM artifacts and pip-install snippets per architecture.
From
→
To
Loading release history…
Legend
PASS All jobs in this pipeline succeededFAIL One or more jobs failedRUNNING Pipeline still in progressN/A No run for this version yet
Cell shows top line a status icon, and bottom linejobs / arch counts (e.g. 14 jobs · 4 arch).
Downloads — ROCm …
CI HUD
Last Updated: --
Loading…
Loading CI HUD data...
Showing 0 of 0 commits
Legend
✓ Passed✗ Failed⏳ Running○ Skipped/N/A
Tip: Click on a commit row to expand and see detailed job status. Click any job status to go to GitHub.
Multi-Arch
Last Updated: --
Loading…
Loading Multi-Arch CI data...
Showing 0 of 0 commits
Legend
✓ Passed✗ Failed⏳ Running○ Skipped/N/A
Tip: Click any category header (▸) to expand it into per-arch status dots. Click a commit row to see all jobs grouped by category.
Recent failures grouped by job name + workflow + arch. Larger clusters mean a stage is broken across many runs — start here when triaging.
Failures
Job pattern
Workflow
Architectures
Repository
Last seen
Action
Loading…
Flake Detection
Jobs where a re-run produced a different result than the original attempt — the test flapped pass↔fail without code changes.
Job
Architecture
Attempt sequence
Repository
Last seen
Action
Loading…
Legend
✓ Attempt passed✗ Attempt failed○ Cancelled
Tip: Click any "Logs" link to jump to the failing job on GitHub. A flake of fail → pass usually means a transient issue (resource, network); pass → fail means a regression slipped past the first run.
Release Notes
Generated: —
Generate notes between two commits
Paste two commit SHAs (7+ hex chars). The lambda will look up their timestamps and pull every PR merged in that window across the selected repos. Tip: copy SHAs from the CI HUD tab. Share with #release-notes?from=SHA1&to=SHA2&repos=ROCm/TheRock.
Time-to-first-review is omitted: our ingestion lambda doesn't subscribe to the pull_request_review webhook event. Adding it requires (1) updating the GitHub webhook subscription, (2) extending the lambda + ClickHouse schema, (3) backfilling. Worth doing if review responsiveness becomes a focus area.
Click contributor or label bars to drill into the Issues tab filtered by author or label.
