Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi355_4: DP EP Distributed NixlConnector PD accuracy tests (4 GPUs) [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#40243•Fetched 2026-04-19 15:04:52
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: mi355_4: DP EP Distributed NixlConnector PD accuracy tests (4 GPUs)

Current streak start: 2026-04-18 First failure in 60d window: 2026-03-31 Last successful nightly: 2026-04-17 Break frequency (60d, pass↔fail flips): 2 Latest nightly date: 2026-04-18 Latest build(s): #7791

Hardware status in latest nightly

hardwarestatus
mi355_4fail

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_4 hardware status and recent changes in the sync_ready_tickets.py script or the test group configuration to resolve the failing test.

Guidance

  • Review the sync_ready_tickets.py script for any recent updates or modifications that might be causing the test group to fail.
  • Check the hardware status of mi355_4 for any issues or errors that could be contributing to the failure.
  • Investigate the test group configuration and recent changes to the test cases or environment that might be causing the failure.
  • Analyze the build history, specifically build #7791, to identify any potential issues or changes that could be related to the failure.

Notes

The issue seems to be related to a specific hardware setup (mi355_4) and a particular test group, so the solution will likely involve investigating and resolving issues with that hardware or test configuration.

Recommendation

Apply workaround: Investigate and resolve hardware or test configuration issues, as the problem seems to be specific to the mi355_4 hardware and test group, rather than a general software issue that would require an upgrade.

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…
#GPU setup#container setup#orchestration issue#cache issue#memory leak

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_4: DP EP Distributed NixlConnector PD accuracy tests (4 GPUs) [2 comments, 1 participants]