-
Notifications
You must be signed in to change notification settings - Fork 0
[unit-test] for UCCCommunicator #4
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
[unit-test] for UCCCommunicator #4
Conversation
|
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run You ask your reviewers to trigger select CI tests on top of 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 either: Add If you have any questions, please reach out to us on Slack at https://slack.vllm.ai. 🚀 |
|
detailed log (the debug logging has been removed from this PR) |
|
@ikryukov do you have time to review and merge ? |
70cea45 to
bacd2c6
Compare
It is ready to merge, thanks! but could you rebase it, since I added co-author lengrongfu to previous commit |
bacd2c6 to
36afd42
Compare
8d52072 to
ed9cf39
Compare
|
@ikryukov rebased , thank you . |
36afd42 to
a65a92f
Compare
ed9cf39 to
a90900f
Compare
add UT just like vllm-project#20759 does
I don't have UCC complied Pytorch to verify either CPU or GPU side.
Can you help ? @ikryukov @lengrongfu