Skip to content

[CI] Parity: replace ROCm nightly with scheduled Preview - #3554

Merged
jithunnair-amd merged 4 commits into
developfrom
ethanwee/parity-preview-replacement
Aug 25, 2026
Merged

[CI] Parity: replace ROCm nightly with scheduled Preview#3554
jithunnair-amd merged 4 commits into
developfrom
ethanwee/parity-preview-replacement

Conversation

@ethanwee1

@ethanwee1 ethanwee1 commented Aug 11, 2026

Copy link
Copy Markdown

Summary

  • replace the retired nightly parity key with preview
  • match the live daily rocm-preview linux-noble-rocm-preview-py3.12-mi350 jobs
  • use the current 8/3/2 default/distributed/inductor fallback matrix

This clean replacement is based on current develop; it supersedes #3406, whose pre-reset history cannot merge without a force-push or unrelated-history merge.

Test plan

  • Parse parity config JSON
  • Compile download_testlogs
  • Parse parity.yml as YAML
  • Verify all 13 test jobs against scheduled pytorch/pytorch run 31344407133
  • Run end-to-end Preview parity dispatch

Dependencies

Land this before the Preview auto-trigger update in #3555 and before retargeting the operational parity PRs.

Made with Cursor

Alignment landing order

This is the root dependency. After it lands, retarget the stacked PRs to develop in this order:

  1. [CI] Parity: discover job topology from workflow YAML #3535 dynamic workflow/prefix/shard discovery
  2. [CI] Parity: fix upstream job links #3536 canonical per-shard job URLs
  3. [CI] Parity: classify newly observed ROCm skips #3523 consolidated classifier rules (independent base; may land earlier)
  4. [CI] Parity: avoid variant-only trunk runs for ROCm Inductor #3559 variant-run filtering
  5. [CI] Parity: skip missing configs without aborting report #3558 graceful missing-config handling
  6. [CI] Parity: preserve partial reports on download failure #3557 partial-report preservation
  7. [CI] Parity: use authoritative flaky-test summaries #3560 authoritative flaky attribution
  8. [CI] Parity: resolve sha=latest on current develop #3556 latest-SHA resolution
  9. [CI] Parity auto-trigger: collect scheduled architectures including Preview #3555 scheduled multi-architecture automation last

Validation: full Preview run 31506711303 and combined Preview+MI350 run 31507307756 both succeeded on matching SHA cf18dda7.

August 25 refresh

  • Merged current ROCm develop and reran JSON, Python, and workflow YAML validation.

  • The previously documented Preview and combined Preview+MI350 runs satisfy the end-to-end checklist item.

Use the live rocm-preview mi350 topology and remove the retired nightly CLI/config key on the current develop history.
Match the unique rocm-preview lane without pinning its OS, Python, or runner suffix so routine upstream renames do not disable auto-parity.
@ethanwee1
ethanwee1 changed the base branch from develop to main August 11, 2026 19:33
@ethanwee1
ethanwee1 changed the base branch from main to develop August 11, 2026 19:36
Use the restored eight-shard default matrix so parity downloads every live MI300 shard.
jithunnair-amd pushed a commit that referenced this pull request Aug 25, 2026
## Summary
- classify Triton kernel, Triton heuristic, and fused-attention tests as
PT2.0 - Inductor
- classify backend skips, including TVM coverage, as PT2.0 - Dynamo
- classify the new `hipSOLVER DnXsytrs requires ROCm >= 7.14` guard as
hipSolver/Magma
- support both dotted and slash-separated test file names

## Dashboard analysis
Reviewed the AI analysis generated on 2026-08-04. It confirms that the
`inductor.test_triton_heuristics` and TVM backend movements are
classifier artifacts addressed by this PR. I also checked the underlying
analyzed mi350 report rather than relying only on the AI
recommendations: all 62 incoming unclassified skips are now covered—60
hipSOLVER version guards and two `inductor.test_fused_attention` tests.

The analysis also reports large historical convolution, distributed,
FSDP, and Misc category movements, but explicitly identifies them as
unrelated collection/classifier churn and does not provide test-level
evidence for a new category rule. This PR does not add speculative broad
rules for those movements.

This PR was split from the earlier parity automation stack and contains
only skip-reason classification changes.

## Test plan
- [x] Run Python syntax, lint, and whitespace checks
- [x] Run the classifier against the analyzed mi350 parity CSV
- [x] Confirm coverage rises from 62 unclassified skips to 0 (100% of
2,877 target tests classified)
- [x] Verify this PR changes only `auto_classify_skip_reasons.py`

## Consolidated classifier coverage

This PR now consolidates #3410 and #3456 in addition to its original
Triton/TVM, DnXsytrs, and fused-attention rules. Added coverage includes
conv2d backward, hipSOLVER xgeev, ROCm 6.4 linalg regressions, CUPTI
profiler tests, block_table, explicit NVIDIA-only tests, and
issue-linked `skipIfRocm` messages.

Validation: Python compilation plus eight focused regression cases
spanning the consolidated and existing rules. The result is a strict
superset of the fork classifier.

## Alignment landing order

Independent of #3554 and safe to land after the downloader/link
foundations. It supersedes closed #3410 and #3456 and is the
consolidated classifier target.

## August 25 refresh
- Merged current ROCm `develop`.

- Recognize both `Need at least 4 CUDA devices` and `Need at least 4
accelerator devices` as `Greater than 4 GPU`.
- Added and passed a focused regression test for both message forms.
@jithunnair-amd
jithunnair-amd merged commit 521694f into develop Aug 25, 2026
4 checks passed
@jithunnair-amd
jithunnair-amd deleted the ethanwee/parity-preview-replacement branch August 25, 2026 20:42
@jithunnair-amd
jithunnair-amd restored the ethanwee/parity-preview-replacement branch August 25, 2026 21:05
@jithunnair-amd
jithunnair-amd deleted the ethanwee/parity-preview-replacement branch August 25, 2026 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants