Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi250_1: e2e Scheduling (1 GPU) [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#40206•Fetched 2026-04-19 15:05:48
View on GitHub
Comments
2
Participants
1
Timeline
6
Reactions
0
Author
AndreasKaratzasAndreasKaratzas
Participants
AndreasKaratzasAndreasKaratzas
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: mi250_1: e2e Scheduling (1 GPU)

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

Hardware status in latest nightly

hardwarestatus
mi250_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 mi250_1: e2e Scheduling (1 GPU) test group to identify the cause of the failure.

Guidance

  • Review the test results and logs from the latest nightly build (#7791) to understand the nature of the failure.
  • Check the hardware status of mi250_1 to ensure it is functioning correctly and not causing the test failure.
  • Analyze the changes made between the last successful nightly (2026-04-17) and the first failure (2026-04-18) to identify potential causes.
  • Verify if similar test groups are passing on other AMD hardware to isolate the issue.

Notes

  • The issue seems to be specific to the mi250_1 hardware, so the solution may involve hardware-specific configurations or fixes.
  • Without more information about the test failure, it's difficult to provide a more specific solution.

Recommendation

  • Apply workaround: Investigate and fix the issue with the mi250_1: e2e Scheduling (1 GPU) test group, as it is currently causing the nightly build 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…
#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [CI Failure]: mi250_1: e2e Scheduling (1 GPU) [2 comments, 1 participants]