Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi250_1: OpenAI API correctness [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#40204•Fetched 2026-04-19 15:05:51
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: OpenAI API correctness

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

Guidance

  • Review the test results for the mi250_1: OpenAI API correctness group to understand the nature of the failure.
  • Check the hardware status of mi250_1 to see if there are any issues that could be contributing to the test failure.
  • Investigate the changes made in the latest nightly build (#7791) to see if they may be related to the test failure.
  • Look into the sync_ready_tickets.py script to understand how it manages the test group and see if there are any issues with the script.

Notes

The issue lacks detailed information about the test failure, 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 fix the issue with the mi250_1 hardware or the OpenAI API correctness test group, as it's likely that one of these is the cause of the failure.

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…
#api#pipeline error#runtime error#dependency conflict#environment setup

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: OpenAI API correctness [2 comments, 1 participants]