vllm - 💡(How to fix) Fix [CI Failure]: mi355_1: V1 Sample + Logits [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#41336Fetched 2026-05-01 05:34:09
View on GitHub
Comments
2
Participants
1
Timeline
8
Reactions
0
Participants
Timeline (top)
added_to_project_v2 ×2commented ×2labeled ×1mentioned ×1

Root Cause

  • Flaky test
  • Can reproduce locally
  • Caused by external libraries (e.g. bug in transformers)

Code Example

FAILED v1/sample/test_logprobs.py::test_spec_decode_logprobs[ngram-raw_logprobs]
FAILED v1/sample/test_logprobs.py::test_spec_decode_logprobs[ngram-processed_logprobs]
RAW_BUFFERClick to expand / collapse

Name of failing test

(command rocm-smi || true) && export VLLM_TEST_GROUP_NAME=mi355_1-v1-sample---logits && export VLLM_ALLOW_DEPRECATED_BEAM_SEARCH=1 && cd /vllm-workspace/tests && pytest -v -s v1/sample && pytest -v -s v1/logits_processors && pytest -v -s v1/test_oracle.py && pytest -v -s v1/test_request.py && pytest -v -s v1/test_outputs.py

Basic information

  • Flaky test
  • Can reproduce locally
  • Caused by external libraries (e.g. bug in transformers)

🧪 Describe the failing test

FAILED v1/sample/test_logprobs.py::test_spec_decode_logprobs[ngram-raw_logprobs]
FAILED v1/sample/test_logprobs.py::test_spec_decode_logprobs[ngram-processed_logprobs]

📝 History of failing test

  • Break frequency (60d, pass↔fail flips): 0
  • Latest nightly date: 2026-04-29
  • Latest build(s): amd-ci #8058
  • Latest hardware status: mi355_1=fail

extent analysis

TL;DR

Investigate the test_spec_decode_logprobs function in v1/sample/test_logprobs.py to identify the cause of the test failures.

Guidance

  • Review the test code for test_spec_decode_logprobs to ensure it is correctly implementing the logic for ngram-raw_logprobs and ngram-processed_logprobs.
  • Verify that the input data and expected outputs for the failed tests are correct and consistent.
  • Check the dependencies and libraries used in the test to ensure they are up-to-date and compatible with the current environment.
  • Run the failed tests in isolation to gather more information about the failure, such as error messages or stack traces.

Notes

The issue seems to be related to a specific test case, and the cause of the failure is not immediately clear. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Investigate and fix the specific test case, as it is not a widespread issue and can be addressed by modifying the test code or input data.

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_1: V1 Sample + Logits [2 comments, 1 participants]