-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[CI/Build] Move quantization tests to tests/quantization/ and align markers #2615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pjh4993
wants to merge
4
commits into
vllm-project:main
Choose a base branch
from
pjh4993:chore/ghi-2614-ci-add-diffusion-quantization-tests
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
4eed47b
[CI/Build] Move quantization tests to tests/quantization/ and align m…
pjh4993 f17df1e
[CI/Build] Add quantization quality tests to nightly diffusion pipeline
pjh4993 385da5d
[CI/Build] Split test_int8_config into CPU config tests and CUDA/NPU …
pjh4993 16db77c
[CI/Build] Enable GPU cleanup for qwen-image quantization quality step
pjh4993 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also modify the following script?
tests/e2e/offline_inference/test_quantization_fp8.py
tests/e2e/offline_inference/run_quantization_e2e.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing this out @yenuo26!
I looked into both files:
tests/e2e/offline_inference/test_quantization_fp8.py:@hardware_test(res={"cuda": "L4"})/@hardware_test(res={"cuda": "H100"})— so they have proper hardware markers at the function levelpytestmark = [pytest.mark.core_model, pytest.mark.diffusion]— still uses the olddiffusionmarkerCUDA Unit Teststep explicitly--ignore=tests/e2e, so these won't be picked up automaticallytests/e2e/offline_inference/run_quantization_e2e.sh:Both files have the same CI coverage gap, but they're e2e tests (L3/L4 tier) rather than unit tests — so the fix approach is different. They'd need a dedicated Buildkite step in
test-merge.ymlortest-nightly.ymlrather than relying on marker-based collection.Could you clarify what you'd like changed? Some options:
pytestmarkto dropdiffusionand align with the individual@hardware_testmarkers (minimal, fits this PR)tests/quantization/, update markers, and add a Buildkite step (bigger scope, maybe a follow-up PR)