[CI]Style: Convert test/ to ruff format(Batch #6)#7141
[CI]Style: Convert test/ to ruff format(Batch #6)#7141wangxiyuan merged 1 commit intovllm-project:mainfrom
test/ to ruff format(Batch #6)#7141Conversation
|
👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:
If CI fails, you can run linting and testing checks locally according Contributing and Testing. |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the code quality and maintainability of the project's unit test suite. By integrating a new set of test files into the Ruff formatting pipeline, it ensures a more uniform and readable codebase. The changes primarily involve stylistic adjustments, import organization, and minor refactorings to align with modern Python best practices, contributing to a more streamlined development workflow. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request applies ruff formatting to a batch of test files under tests/ut/. The changes are purely stylistic, including reformatting imports, function calls, and removing unused variables. The modifications correctly apply the linter rules and improve code consistency and readability without altering functionality. I have reviewed the changes and found no issues.
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
test/ to ruff format(Batch #6)test/ to ruff format(Batch #6)
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
### What this PR does / why we need it? | File Path | | :--- | | `tests/ut/batch_invariant/test_batch_invariant.py` | | `tests/ut/compilation/test_acl_graph.py` | | `tests/ut/compilation/test_npugraph_ex_utils_check.py` | | `tests/ut/conftest.py` | | `tests/ut/core/test_scheduler_dynamic_batch.py` | | `tests/ut/device_allocator/test_camem.py` | | `tests/ut/device_allocator/test_cpu_binding.py` | | `tests/ut/distributed/device_communicators/test_pyhccl.py` | | `tests/ut/distributed/device_communicators/test_pyhccl_wrapper.py` | | `tests/ut/distributed/mooncake/test_config_data.py` | | `tests/ut/distributed/test_communicator.py` | | `tests/ut/distributed/test_parallel_state.py` | | `tests/ut/eplb/adaptor/test_vllm_adaptor.py` | | `tests/ut/eplb/core/policy/test_policy_abstract.py` | | `tests/ut/eplb/core/policy/test_policy_default_eplb.py` | | `tests/ut/eplb/core/policy/test_policy_factor.py` | | `tests/ut/eplb/core/policy/test_policy_swift_balancer.py` | | `tests/ut/eplb/core/test_eplb_device_transfer_loader.py` | | `tests/ut/eplb/core/test_eplb_utils.py` | | `tests/ut/spec_decode/test_eagle_proposer.py` | | `tests/ut/test_ascend_config.py` | | `tests/ut/test_envs.py` | | `tests/ut/test_platform.py` | | `tests/ut/test_utils.py` | | `tests/ut/worker/test_block_table.py` | | `tests/ut/worker/test_pcp_manager.py` | | `tests/ut/worker/test_worker_v1.py` | ### Does this PR introduce _any_ user-facing change? ### How was this patch tested? - vLLM version: v0.16.0 - vLLM main: vllm-project/vllm@4034c3d Signed-off-by: MrZ20 <2609716663@qq.com> Signed-off-by: tfhddd <2272751277@qq.com>
…-project#7141) ### What this PR does / why we need it? | File Path | | :--- | | `tests/ut/batch_invariant/test_batch_invariant.py` | | `tests/ut/compilation/test_acl_graph.py` | | `tests/ut/compilation/test_npugraph_ex_utils_check.py` | | `tests/ut/conftest.py` | | `tests/ut/core/test_scheduler_dynamic_batch.py` | | `tests/ut/device_allocator/test_camem.py` | | `tests/ut/device_allocator/test_cpu_binding.py` | | `tests/ut/distributed/device_communicators/test_pyhccl.py` | | `tests/ut/distributed/device_communicators/test_pyhccl_wrapper.py` | | `tests/ut/distributed/mooncake/test_config_data.py` | | `tests/ut/distributed/test_communicator.py` | | `tests/ut/distributed/test_parallel_state.py` | | `tests/ut/eplb/adaptor/test_vllm_adaptor.py` | | `tests/ut/eplb/core/policy/test_policy_abstract.py` | | `tests/ut/eplb/core/policy/test_policy_default_eplb.py` | | `tests/ut/eplb/core/policy/test_policy_factor.py` | | `tests/ut/eplb/core/policy/test_policy_swift_balancer.py` | | `tests/ut/eplb/core/test_eplb_device_transfer_loader.py` | | `tests/ut/eplb/core/test_eplb_utils.py` | | `tests/ut/spec_decode/test_eagle_proposer.py` | | `tests/ut/test_ascend_config.py` | | `tests/ut/test_envs.py` | | `tests/ut/test_platform.py` | | `tests/ut/test_utils.py` | | `tests/ut/worker/test_block_table.py` | | `tests/ut/worker/test_pcp_manager.py` | | `tests/ut/worker/test_worker_v1.py` | ### Does this PR introduce _any_ user-facing change? ### How was this patch tested? - vLLM version: v0.16.0 - vLLM main: vllm-project/vllm@4034c3d Signed-off-by: MrZ20 <2609716663@qq.com>
…-project#7141) ### What this PR does / why we need it? | File Path | | :--- | | `tests/ut/batch_invariant/test_batch_invariant.py` | | `tests/ut/compilation/test_acl_graph.py` | | `tests/ut/compilation/test_npugraph_ex_utils_check.py` | | `tests/ut/conftest.py` | | `tests/ut/core/test_scheduler_dynamic_batch.py` | | `tests/ut/device_allocator/test_camem.py` | | `tests/ut/device_allocator/test_cpu_binding.py` | | `tests/ut/distributed/device_communicators/test_pyhccl.py` | | `tests/ut/distributed/device_communicators/test_pyhccl_wrapper.py` | | `tests/ut/distributed/mooncake/test_config_data.py` | | `tests/ut/distributed/test_communicator.py` | | `tests/ut/distributed/test_parallel_state.py` | | `tests/ut/eplb/adaptor/test_vllm_adaptor.py` | | `tests/ut/eplb/core/policy/test_policy_abstract.py` | | `tests/ut/eplb/core/policy/test_policy_default_eplb.py` | | `tests/ut/eplb/core/policy/test_policy_factor.py` | | `tests/ut/eplb/core/policy/test_policy_swift_balancer.py` | | `tests/ut/eplb/core/test_eplb_device_transfer_loader.py` | | `tests/ut/eplb/core/test_eplb_utils.py` | | `tests/ut/spec_decode/test_eagle_proposer.py` | | `tests/ut/test_ascend_config.py` | | `tests/ut/test_envs.py` | | `tests/ut/test_platform.py` | | `tests/ut/test_utils.py` | | `tests/ut/worker/test_block_table.py` | | `tests/ut/worker/test_pcp_manager.py` | | `tests/ut/worker/test_worker_v1.py` | ### Does this PR introduce _any_ user-facing change? ### How was this patch tested? - vLLM version: v0.16.0 - vLLM main: vllm-project/vllm@4034c3d Signed-off-by: MrZ20 <2609716663@qq.com> Signed-off-by: guxin108 <1252896542@qq.com>
What this PR does / why we need it?
tests/ut/batch_invariant/test_batch_invariant.pytests/ut/compilation/test_acl_graph.pytests/ut/compilation/test_npugraph_ex_utils_check.pytests/ut/conftest.pytests/ut/core/test_scheduler_dynamic_batch.pytests/ut/device_allocator/test_camem.pytests/ut/device_allocator/test_cpu_binding.pytests/ut/distributed/device_communicators/test_pyhccl.pytests/ut/distributed/device_communicators/test_pyhccl_wrapper.pytests/ut/distributed/mooncake/test_config_data.pytests/ut/distributed/test_communicator.pytests/ut/distributed/test_parallel_state.pytests/ut/eplb/adaptor/test_vllm_adaptor.pytests/ut/eplb/core/policy/test_policy_abstract.pytests/ut/eplb/core/policy/test_policy_default_eplb.pytests/ut/eplb/core/policy/test_policy_factor.pytests/ut/eplb/core/policy/test_policy_swift_balancer.pytests/ut/eplb/core/test_eplb_device_transfer_loader.pytests/ut/eplb/core/test_eplb_utils.pytests/ut/spec_decode/test_eagle_proposer.pytests/ut/test_ascend_config.pytests/ut/test_envs.pytests/ut/test_platform.pytests/ut/test_utils.pytests/ut/worker/test_block_table.pytests/ut/worker/test_pcp_manager.pytests/ut/worker/test_worker_v1.pyDoes this PR introduce any user-facing change?
How was this patch tested?