-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
LoRA Support for Ultravox model #11253
base: main
Are you sure you want to change the base?
LoRA Support for Ultravox model #11253
Conversation
👋 Hi! Thank you for contributing to the vLLM project. Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can do one of these:
🚀 |
Hi folks, I'm working with @petersalas on this. PR is not complete but wanted to start the discussion as I have some open questions and need some help from vLLM community |
This pull request has merge conflicts that must be resolved before it can be |
771484d
to
64a664f
Compare
Signed-off-by: Sumit Vij <[email protected]>
WIP: lora tests Minor tweaks Moar fixes Temp changes Cleanup Add more debugging logs and packed modules Signed-off-by: Sumit Vij <[email protected]>
Remove stale comment Add llama lora modules Add llama test case Add test case and log warning on missing lora modules Rollback unwanted changes and format fixes Signed-off-by: Sumit Vij <[email protected]>
64a664f
to
3f5996c
Compare
Can you refer to #10022 to minimize the changes? |
Changes are inline with 10022 except the test case and other minor logging changes. Do you have any concerns with any particular change? |
It looks like there are issues with both the added tests and logs. We should only modify the Ultravox scipt, following the changes made in the #10022 |
What is/are the issue(s)? Maybe I miss something but tests are passing |
@jeejeelee lmk what are your concerns please? Happy to address it. Having a test case was super helpful to make sure LoRA works as expected with llama and ultravox |
@thedebugger We should only modify |
@jeejeelee does the PR now looks okay to you? The changes are only related to ultravox and ultravox test. And, I'll open up another PR related to missing lora modules warning message Note: AFAICT, CI and GPU tests are failing for unrelated reason which I also see happening it in other PRs that have been merged into main |
Signed-off-by: Sumit Vij <[email protected]>
dd686e3
to
4a633d3
Compare
@@ -858,7 +865,8 @@ def generate_greedy_logprobs( | |||
greedy_logprobs_params, | |||
images=images, | |||
audios=audios, | |||
videos=videos) | |||
videos=videos, | |||
**kwargs) | |||
|
|||
def generate_encoder_decoder_greedy_logprobs( | |||
self, |
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.
The changes to this file are not related to this PR, please revert.
After completing the above modifications, this PR can be merged, thanks |
…-ultravox-lora-dec-16
Signed-off-by: Jee Jee Li <[email protected]>
…-ultravox-lora-dec-16
Signed-off-by: Jee Jee Li <[email protected]>
@petersalas does PR look good to you? If yes, please approve |
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.
LGTM
@jeejeelee okay to approve and merge? |
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.
Let's wait for the lora test issue mentioned in #12111 to be resolved before considering starting the merge testing.
|
…-ultravox-lora-dec-16
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.
Let's keep the unit tests as they are for now. I'll look into how to train Ultravox LoRA and update in another PR
@jeejeelee I'll fix the test tomorrow. I pulled up the latest code and it is failing for me with Cuda OOM (different than CI failure). I also ran the test again on 208e662, it works. So likely something changed on master that is causing test to fail. AFAICT, the failure is not related to LoRA, so training ultravox lora shouldn't have any impact. Let me troubleshoot this tomorrow and figure out what is going on before you spend time on this. |
I spent more time looking at the failure. The failure happens during init when running ultravox with dummy data and I haven't been able to reproduce it locally (though locally test fails with cuda oom error for llama on latest version). I'll look further tomorrow why CI is seeing device mismatch when running whisper. I checked the other ultravox test, that is working fine. I'll look further into it tomorrow |
We can first remove the LoRA test-related code and merge this PR. I'll spend some time later training a LoRA model. What do you think? |
Head branch was pushed to by a user without write access
Signed-off-by: Sumit Vij <[email protected]> Reduce model len Signed-off-by: Sumit Vij <[email protected]>
d247036
to
1195ad8
Compare
This should also work w/ mistral models which also uses LlamaForCasualLM architecture re: here