Repository navigation
[TEST][XPU][CI] disable xpu tests for nonexistent input norm kernels - #59568
jikunshang merged 4 commits into
Conversation
|
/pr-checklist |
|
@jikunshang could you take a look? |
Signed-off-by: Milosz Grunwald <milosz.grunwald@intel.com>
5f299f8 to
1c259e2
Compare
|
as per request from @jikunshang I've changed the implementation from python decorator to |
|
/ci run --allow-stale |
|
✅ Triggered Buildkite CI #92575 for commit
|
Signed-off-by: Milosz Grunwald <milosz.grunwald@intel.com>
373712b to
efe65c7
Compare
|
/ci run |
|
✅ Triggered Buildkite CI #92635 for commit |
CI selector (shadow): 0 test steps (0 jobs) instead of 0 (0 jobs)Shadow mode: this changes nothing about what CI runs. It shows what the evidence-based selector would pick for this PR, next to today's rules. How it works. Feedback welcome: reply here if it would skip a step this change needs, or runs something unrelated.
Selector would run (0)none Would skip (today's rules run them) (0)none Would add (today's rules do not run them) (0)none AMD mirrors: would skip (0)none AMD mirrors: would add (0)none 2 changed files · base |
…kernels (vllm-project#59568)" This reverts commit 8c3b720. Signed-off-by: Yan Ma <yan.ma@intel.com>
Overview
#59195 introduced override of FusedMMInputNorm.enabled(), now it always returns True; This forces tests of FusedMMInputNorm on float based XPU kernels that do not exist. This pr disables those tests.
Claims
Stop testing missing kernels, keep the working uint8 path
Validation
Details
Pull Request Checklist
I used vLLM's
/pr-checklistskill. (Mandatory for agents, optional for humans).AI assistance was used during the creation of this PR.
Design Fit: Minimizes impact on core components, reuses existing functionality, and justifies added complexity.
Testing and Validation: Validates the change and ensures any added tests are meaningful and reliable, with CI coverage or documented CI resource constraints and validation performed outside CI.
Code Quality and Style: Keeps code and comments clear and concise, and updates relevant documentation and examples.
Pull Request Contents: Includes a brief summary and relevant links, supports claims with evidence, explains root causes and implementation trade-offs, and follows the contributing guide.