[CI] Serialize libcu++ lit tests on GB300 - #11223
Conversation
|
/ok to test 24e4c33 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe CI matrix adds an ARM64 GB300 libcudacxx override and sets single-process lit execution for both the override and nightly lanes. ChangesGB300 libcudacxx CI
Merge Risk: ⚪ Minimal · up to The GB300 libcudacxx CI lanes now run lit with one worker, avoiding concurrent CUDA work while preserving the intended test execution. The configuration is ready to merge. Comment |
🥳 CI Workflow Results🟩 Finished in 53m 38s: Pass: 100%/2 | Total: 52m 46s | Max: 32m 02s | Hits: 19%/15138See results here. AI failure analysis1. Pull-request workflow override rejected by merge gate · 1 jobExplanation: The selected GB300 libcudacxx build and test both passed, but the workflow intentionally fails whenever `workflows.override` is non-empty. The final `CI` job is derivative and failed only because this merge gate failed. Evidence: Copy this prompt into a coding agentJobs: |
GB300 nodes have a known issue when CUDA work is submitted concurrently from multiple processes. Limit the GB300 libcu++ lit job to one worker; a temporary override runs the serialized job on this PR before the nightly setting is merged.