Issue Station
Sign In
Tools hereToolbox

vllm - ✅(Solved) Fix [CI Failure]: mi250_1: LoRA %N [1 pull requests, 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#40261•Fetched 2026-04-19 15:04:38
View on GitHub
Comments
1
Participants
1
Timeline
7
Reactions
0
Author
AndreasKaratzasAndreasKaratzas
Participants
AndreasKaratzasAndreasKaratzas
Timeline (top)
added_to_project_v2 ×2project_v2_item_status_changed ×2commented ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #40272: [CI/Build][AMD] Align LoRA %N shard ignore list with generic LoRA shard

Description (problem / solution / changelog)

Purpose

Fixes #40261 by aligning the AMD LoRA %N Buildkite step with the generic LoRA shard configuration.

Test Plan

CI should ignore the test

Test Result

<details> <summary> Essential Elements of an Effective PR Description Checklist </summary>
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
</details>

Changed files

  • .buildkite/test-amd.yaml (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi250_1: LoRA %N

Current streak start: 2026-04-16 First failure in 60d window: 2026-04-16 Last successful nightly: 2026-04-15 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-ci-dashboard/actions/runs/24613460306

extent analysis

TL;DR

The most likely fix involves investigating and resolving the issue with the mi250_1: LoRA %N test group on AMD hardware.

Guidance

  • Investigate the test failures in the mi250_1: LoRA %N group to identify the root cause of the issue.
  • Check the hardware status and test results for any patterns or clues that could indicate the source of the problem.
  • Review the changes made between the last successful nightly (2026-04-15) and the first failure (2026-04-16) to see if any code or configuration changes may have contributed to the issue.
  • Verify the test environment and setup for the mi250_1 hardware to ensure it is correctly configured and functioning as expected.

Notes

The issue seems to be specific to the mi250_1: LoRA %N test group on AMD hardware, and resolving the issue will likely require a detailed investigation of the test failures and the hardware setup.

Recommendation

Apply workaround: Investigate and resolve the test failures in the mi250_1: LoRA %N group, as the issue appears to be specific to this test group and hardware 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…
#API routing#API middleware#SSR setup#ISR setup#authentication 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 - ✅(Solved) Fix [CI Failure]: mi250_1: LoRA %N [1 pull requests, 1 comments, 1 participants]