vllm - 💡(How to fix) Fix [CI Failure]: mi355_1: Kernels Quantization Test 2 [1 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#40230Fetched 2026-04-19 15:05:12
View on GitHub
Comments
1
Participants
1
Timeline
8
Reactions
0
Participants
Timeline (top)
project_v2_item_status_changed ×3added_to_project_v2 ×2closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi355_1: Kernels Quantization Test 2

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
mi355_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 mi355_1: Kernels Quantization Test 2 group to identify the cause of the failing test.

Guidance

  • Review the test logs and output from the mi355_1 hardware to understand the failure mode.
  • Check the test code and configuration for any recent changes that may be contributing to the failure.
  • Verify that the mi355_1 hardware is functioning correctly and that there are no environmental or configuration issues.
  • Investigate the sync_ready_tickets.py script to ensure it is correctly managing the test group and reporting failures.

Notes

The issue lacks detailed information about the failure, so a thorough investigation of the test group and hardware is necessary to identify the root cause.

Recommendation

Apply workaround: Investigate and debug the failing test group to identify the root cause and apply a fix or workaround as needed, rather than relying on an upgrade or automated script.

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