vllm - 💡(How to fix) Fix [CI Failure]: mi355_2: Qwen3-30B-A3B-FP8-block Accuracy (B200-MI355) [1 comments, 2 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#40526Fetched 2026-04-22 07:44:05
View on GitHub
Comments
1
Participants
2
Timeline
15
Reactions
0
Timeline (top)
mentioned ×3project_v2_item_status_changed ×3subscribed ×3added_to_project_v2 ×2
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi355_2: Qwen3-30B-A3B-FP8-block Accuracy (B200-MI355)

Current streak start: 2026-04-21 First failure in 60d window: 2026-04-21 Last successful nightly: 2026-04-20 Break frequency (60d, pass↔fail flips): 1 Latest nightly date: 2026-04-21 Latest build(s): amd-ci #7854

Hardware status in latest nightly

hardwarestatus
mi355_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 mi355_2 hardware status and the recent changes in the nightly build to identify the cause of the failing test group.

Guidance

  • Review the build logs for amd-ci #7854 to check for any errors or warnings that might indicate the cause of the failure.
  • Investigate the hardware status of mi355_2 to determine if there are any issues with the hardware configuration or environment.
  • Check the test group Qwen3-30B-A3B-FP8-block Accuracy (B200-MI355) to see if there have been any recent changes to the test cases or data that could be causing the failure.
  • Compare the latest nightly build with the last successful nightly build from 2026-04-20 to identify any changes that might have introduced the failure.

Notes

The issue seems to be related to a specific hardware and test group, so the investigation should focus on these areas. The fact that the test group was passing previously and started failing recently suggests that there might be a change in the environment, hardware, or test cases that is causing the failure.

Recommendation

Apply workaround: Investigate and fix the issue with the mi355_2 hardware or the test group, as the problem seems to be specific to this 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

vllm - 💡(How to fix) Fix [CI Failure]: mi355_2: Qwen3-30B-A3B-FP8-block Accuracy (B200-MI355) [1 comments, 2 participants]