Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi250_2: Plugin Tests (2 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#40480•Fetched 2026-04-22 07:45:14
View on GitHub
Comments
0
Participants
1
Timeline
7
Reactions
0
Author
AndreasKaratzasAndreasKaratzas
Participants
AndreasKaratzasAndreasKaratzas
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: mi250_2: Plugin Tests (2 GPUs)

Current streak start: 2026-04-21 First failure in 60d window: 2026-04-15 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
mi250_2fail

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 mi250_2 hardware status and recent changes in the Plugin Tests (2 GPUs) group to identify the cause of the failing test.

Guidance

  • Review the build logs from amd-ci #7854 to identify any error messages or warnings related to the mi250_2 hardware.
  • Check the sync_ready_tickets.py script for any recent changes or updates that may be contributing to the test failures.
  • Verify that the mi250_2 hardware is properly configured and functioning correctly.
  • Investigate the test history to see if there are any patterns or correlations between the test failures and specific hardware or software configurations.

Notes

The issue lacks detailed information about the test failures, so it's difficult to provide a more specific solution. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply workaround: Investigate and address the mi250_2 hardware status and test configuration to resolve the failing test group, as the issue seems to be related to a specific hardware or test setup rather than a software version issue.

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…
#tensor shape#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

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

Back to top recommendations

TRENDING