Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix [CI Failure]: mi355_2: Distributed Tests (2xH100-2xMI355) [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#40522•Fetched 2026-04-22 07:44:11
View on GitHub
Comments
0
Participants
1
Timeline
7
Reactions
0
Author
AndreasKaratzasAndreasKaratzas
Participants
AndreasKaratzasAndreasKaratzas
Timeline (top)
project_v2_item_status_changed ×3added_to_project_v2 ×2closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

AMD nightly — failing test group

Group: mi355_2: Distributed Tests (2xH100-2xMI355)

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
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 Distributed Tests group to identify the cause of the failing test.

Guidance

  • Review the latest nightly build (amd-ci #7854) to check for any errors or warnings related to the mi355_2 hardware.
  • Check the sync_ready_tickets.py script to ensure it is correctly managing the test group and hardware status.
  • Verify the test environment and configuration for the Distributed Tests group to ensure it is set up correctly for the mi355_2 hardware.
  • Investigate the test results and logs to identify the specific test or tests that are failing and causing the group to fail.

Notes

The issue lacks detailed information about the test failures, so further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and resolve the issue with the mi355_2 hardware status and the Distributed Tests group, as the problem seems to be specific to this hardware and test group.

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…
#dependency conflict#environment setup#docker error#permission error#memory optimization

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: Distributed Tests (2xH100-2xMI355) [1 participants]