vllm - 💡(How to fix) Fix [CI Failure]: mi355_1: Multi-Modal Models (Standard) 4: other + whisper [2 comments, 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#40236Fetched 2026-04-19 15:05:03
View on GitHub
Comments
2
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
added_to_project_v2 ×2commented ×2labeled ×1project_v2_item_status_changed ×1
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi355_1: Multi-Modal Models (Standard) 4: other + whisper

Current streak start: 2026-04-10 First failure in 60d window: 2026-03-31 Last successful nightly: 2026-04-09 Break frequency (60d, pass↔fail flips): 2 Latest nightly date: 2026-04-18 Latest build(s): #7791

Hardware status in latest nightly

hardwarestatus
mi355_1fail

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-internal-project-dashboard/actions/runs/24602867596

extent analysis

TL;DR

Investigate the mi355_1 hardware status and the Multi-Modal Models (Standard) 4: other + whisper test group to identify the cause of the failing test.

Guidance

  • Review the test results and logs from the mi355_1 hardware to determine the specific reason for the test failure.
  • Check the test configuration and parameters for the Multi-Modal Models (Standard) 4: other + whisper test group to ensure they are correct and consistent with previous successful runs.
  • Compare the test results from the last successful nightly (2026-04-09) with the latest failing nightly (2026-04-18) to identify any changes or differences that may be contributing to the failure.
  • Consider re-running the test on the mi355_1 hardware with the same configuration and parameters as the last successful nightly to see if the failure is reproducible.

Notes

The issue may be related to a change in the test configuration, hardware issues, or other environmental factors, but more information is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and address the specific cause of the test failure on the mi355_1 hardware, rather than attempting a general fix, as the issue appears to be specific to this test group and hardware 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