Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi300_2: GPQA Eval (GPT-OSS) (2xH100-2xMI300) [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#40506•Fetched 2026-04-22 07:44:35
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
AndreasKaratzasAndreasKaratzas
Participants
AndreasKaratzasAndreasKaratzas
Timeline (top)
added_to_project_v2 ×2closed ×1labeled ×1project_v2_item_status_changed ×1
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi300_2: GPQA Eval (GPT-OSS) (2xH100-2xMI300)

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
mi300_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 mi300_2 hardware status and the latest nightly build to identify the cause of the failing test group.

Guidance

  • Check the build logs for amd-ci #7854 to see if there are any error messages or warnings that could indicate the cause of the failure.
  • Review the hardware status table to see if there are any other hardware components that are failing or showing unusual behavior.
  • Investigate the sync_ready_tickets.py script to understand how it is managing the test group and if there are any potential issues with the script itself.
  • Look at the history of the test group to see if there have been any recent changes or updates that could be contributing to the failure.

Notes

The issue seems to be related to a specific hardware component (mi300_2) and a particular test group, so the solution will likely involve investigating the hardware and the test group specifically.

Recommendation

Apply workaround: Investigate and fix the mi300_2 hardware issue or update the test group configuration to avoid the failing hardware.

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…
#agent setup#task chaining#parallel task#integration issue#index 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]: mi300_2: GPQA Eval (GPT-OSS) (2xH100-2xMI300) [1 participants]