Skip to content

integration-vllm-test #2258

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

Merged
merged 1 commit into from
May 28, 2025
Merged

integration-vllm-test #2258

merged 1 commit into from
May 28, 2025

Conversation

drisspg
Copy link
Contributor

@drisspg drisspg commented May 24, 2025

Stacked PRs:


integration-vllm-test

Copy link

pytorch-bot bot commented May 24, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/2258

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit d152dac with merge base 1017c7e (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

drisspg added a commit that referenced this pull request May 24, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from f27fa03 to c0107a3 Compare May 24, 2025 00:00
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 24, 2025
@drisspg drisspg changed the base branch from drisspg/stack/57 to main May 24, 2025 00:35
drisspg added a commit that referenced this pull request May 24, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from c0107a3 to b0e4da1 Compare May 24, 2025 00:35
@drisspg drisspg changed the base branch from main to drisspg/stack/57 May 24, 2025 00:35
@drisspg drisspg changed the base branch from drisspg/stack/57 to main May 24, 2025 17:12
drisspg added a commit that referenced this pull request May 24, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from b0e4da1 to c7e639e Compare May 24, 2025 17:12
@drisspg drisspg changed the base branch from main to drisspg/stack/57 May 24, 2025 17:12
@drisspg drisspg changed the base branch from drisspg/stack/57 to main May 24, 2025 17:42
drisspg added a commit that referenced this pull request May 24, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from c7e639e to d12188b Compare May 24, 2025 17:42
@drisspg drisspg changed the base branch from main to drisspg/stack/57 May 24, 2025 17:42
@drisspg drisspg changed the base branch from drisspg/stack/57 to main May 27, 2025 20:36
drisspg added a commit that referenced this pull request May 27, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from d12188b to c06d97f Compare May 27, 2025 20:36
@drisspg drisspg added the topic: not user facing Use this tag if you don't want this PR to show up in release notes label May 27, 2025
drisspg added a commit that referenced this pull request May 27, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from c06d97f to edd42f9 Compare May 27, 2025 21:57
drisspg added a commit that referenced this pull request May 27, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from edd42f9 to f4bcd2d Compare May 27, 2025 22:17
drisspg added a commit that referenced this pull request May 27, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from f4bcd2d to 1fc853f Compare May 27, 2025 22:23
drisspg added a commit that referenced this pull request May 27, 2025
stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from 1fc853f to 3066141 Compare May 27, 2025 23:02
Comment on lines 104 to 105
os.environ["VLLM_USE_V1"] = "1"
os.environ["VLLM_ENABLE_V1_MULTIPROCESSING"] = "0"
os.environ["VLLM_TEST_STANDALONE_COMPILE"] = "1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you missing VLLM_DISABLE_COMPILE_CACHE?

can you write down for each flag about whether they are always required v.s. temporary etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made note here: #2239

You can see that VLLM_TEST_STANDALONE_COMPILE which wil lultimately be the default doesn't makes it so that we can compile subclasses

Copy link
Contributor Author

@drisspg drisspg May 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good point, I think we should actually just set this in AO integration upstream

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean modify these flags when people use AO?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, in the AO integration if someone is loading an AO model we should just sset this flag I will make a PR

print(f"Quick test - Input: {test_input}, Output: {decoded}")

# Save quantized model
print(f"Saving quantized model to {output_dir}...")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we delete these in the end?

stack-info: PR: #2258, branch: drisspg/stack/58
@drisspg drisspg force-pushed the drisspg/stack/58 branch from 3066141 to d152dac Compare May 28, 2025 00:43
@drisspg drisspg merged commit 4d5f657 into main May 28, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. topic: not user facing Use this tag if you don't want this PR to show up in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants