vllm - 💡(How to fix) Fix [CI Failure]: mi325_4: LM Eval Large Models (4xH100-4xMI325) [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#40517Fetched 2026-04-22 07:44:19
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: LM Eval Large Models (4xH100-4xMI325)

Current streak start: 2026-04-21 First failure in 60d window: 2026-04-21 Last successful nightly:Break frequency (60d, pass↔fail flips): 0 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 hardware status and the latest nightly build to identify the cause of the failing test group.

Guidance

  • Review the amd-ci #7854 build to check for any errors or warnings that may indicate the cause of the failure.
  • Check the sync_ready_tickets.py script to ensure it is correctly managing the test group and updating the status.
  • Investigate the hardware status of mi325_4 to determine if there are any issues with the hardware configuration or environment.
  • Verify that the test group is correctly configured and that all dependencies are met.

Notes

The issue lacks detailed information about the error messages or logs, making it difficult to provide a more specific solution.

Recommendation

Apply workaround: Investigate and resolve the issue with the mi325_4 hardware status and the latest nightly build, as it is likely causing the test group to fail.

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