[CI/Build] Cleanup LoRA test

[jeejeelee]

Purpose

Test Plan

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

[gemini-code-assist]

Code Review

This pull request aims to clean up LoRA tests by removing redundant decorators and parameters. While most changes appear to be correct refactoring, I have identified a critical issue in tests/lora/test_mixtral.py where a change will cause a TypeError and break the test. Additionally, I've raised concerns about the removal of the @create_new_process_for_each_test decorator from single-GPU tests, which could potentially lead to test flakiness due to resource leakage.

[DarkLight1337]

Could you elaborate why create_new_process_for_each_test can be removed?

[jeejeelee]

Could you elaborate why create_new_process_for_each_test can be removed?

See:https://github.com/vllm-project/vllm/blob/main/tests/utils.py#L1082