vllm - 💡(How to fix) Fix [CI Failure]: mi325_4: Distributed Compile + Comm (4 GPUs) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#40516Fetched 2026-04-22 07:44:20
View on GitHub
Comments
0
Participants
1
Timeline
7
Reactions
0
Participants
Timeline (top)
project_v2_item_status_changed ×3added_to_project_v2 ×2closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi325_4: Distributed Compile + Comm (4 GPUs)

Current streak start: 2026-04-21 First failure in 60d window: 2026-04-09 Last successful nightly: 2026-04-20 Break frequency (60d, pass↔fail flips): 3 Latest nightly date: 2026-04-21 Latest build(s): amd-ci #7854

Hardware status in latest nightly

hardwarestatus
mi325_4fail

Auto-managed by sync_ready_tickets.py. Closed + moved to Done when this group passes on all AMD hardware.

Last sync: https://github.com/AndreasKaratzas/vllm-ci-dashboard/actions/runs/24731404470

extent analysis

TL;DR

Investigate the mi325_4: Distributed Compile + Comm (4 GPUs) test group failure to identify the root cause of the issue.

Guidance

  • Review the build logs from amd-ci #7854 to identify potential errors or warnings that may be contributing to the test failure.
  • Check the hardware status of mi325_4 to ensure that it is functioning correctly and not experiencing any issues that could be causing the test failure.
  • Investigate the changes made between the last successful nightly (2026-04-20) and the current failing nightly (2026-04-21) to determine if any recent changes may be contributing to the issue.
  • Consider re-running the test group on the mi325_4 hardware to see if the issue is intermittent or consistently failing.

Notes

The issue appears to be related to a specific test group and hardware configuration, so any investigation or debugging should focus on this area.

Recommendation

Apply workaround: Investigate and address the root cause of the test failure, as the issue is likely specific to the mi325_4 hardware or test group configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING