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.
A release event = the workflow runs sharing one (repo, head_sha) per nightly. Shows up here once the next nightly fires multi_arch_release.yml + the wheel workflows + dispatched test_artifacts.yml runs.
Lane
Linux
Windows
Loading…
Legend
✓ Passed✗ Failed◉ Running / queued○ Empty / N/AItalic cell = workflow run is OS-combined (mirrored into both columns).
Test Artifacts Runs
No test_artifacts.yml runs in the selected window.
Filled in once the post-PR-5212 release/CI workflows start dispatching test runs. Try widening the window to 30 days.
Loading…
Legend
✓ Passed✗ Failed◉ Running· No run for this familySame SHA on the same day → one row; multiple test runs for one family on that day → worst-status wins.
PASS Build/Test SuccessfulFAIL Build/Test FailedSKIPPED SkippedIN PROGRESS Currently RunningCANCELLED CancelledPENDING Waiting to Start
Time format: Run time +Queue time
Build Metrics
Last Updated: --
Component build-time extremes
Per spec 2.3 / 2.4 — fixed periods (week / month / quarter), independent of the granularity dropdown above.
Loading…
Overall build time per technology
Wall-clock duration (run started → completed). Dashed line = trailing moving average.
Build time per component
Mean per-job execution time, classified into ROCm component categories. Click a series in the legend to toggle visibility.
Build stability per technology
Per spec 3.1. Bars = run counts (success vs failure); the line = success rate %. Bucketing follows the granularity dropdown (week / month / quarter — daily granularity is intentionally not exposed here, sample size too small).
About this tab
Implements sections 2 + 3 of the Build Metrics spec. Package-size visuals (section 6) and regression alerts (section 4) are tracked as Phase C / D and ship in follow-up PRs.
Submodule Bump PRs
Last Updated: --
Bump History
Recent bump activity for tracked submodules. Click any PR to open it on GitHub.
Open Bump PRs
Pull requests updating submodule versions in TheRock. Click ▸ on a tracked-submodule row to see what upstream PRs that bump pulls in.
PR
Submodule
Upstream span
Title
Author
Status
CI Checks
Age
Updated
Loading bump PR data...
Submodule Version Status
Current submodule versions from .gitmodules
Submodule
Path
Current SHA
Pending Bump PR
Last Bumped
Loading submodule status...
Recently Merged Bump PRs
PR
Submodule
Upstream span
Title
Author
Merged
Loading merged PRs...
Legend
OPEN PR is openREVIEW Awaiting reviewDRAFT Draft PRCHANGES Changes requestedAPPROVED ApprovedMERGED Merged
10+ Significantly behind upstream1-9 Slightly behind0 Up to date
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.
