[CI] fix skiped e2e test when upgrade vllm version

[Meihan-chen]

What this PR does / why we need it?

fix skiped test_aclgraph_capture_replay.py when upgrade vllm version

Does this PR introduce any user-facing change?

How was this patch tested?

• vLLM version: v0.15.0
• vLLM main: vllm-project/vllm@1339784

[gemini-code-assist]

Summary of Changes

Hello @Meihan-chen, I'm Gemini Code Assist¹! 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 addresses a continuous integration issue by re-enabling two previously skipped end-to-end tests. These tests, related to ACLGraph capture/replay and Llama32 LoRA functionality, are now integrated back into the CI pipeline to ensure comprehensive validation, particularly after VLLM version upgrades. This change improves the robustness of the testing suite and prevents regressions.

Highlights

• E2E Test Re-enablement: Re-enabled the test_aclgraph_capture_replay end-to-end test by removing the @pytest.mark.skip decorator, allowing it to run as part of the CI pipeline.
• Llama LoRA Test Activation: Activated the test_llama_lora end-to-end test by removing its @pytest.mark.skip decorator, ensuring its execution during CI to validate Llama32 LoRA functionality.

🧠 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

• tests/e2e/multicard/2-cards/test_aclgraph_capture_replay.py
  • Removed the @pytest.mark.skip decorator from the _run_worker_process test function.
• tests/e2e/singlecard/test_llama32_lora.py
  • Removed the @pytest.mark.skip decorator from the test_llama_lora test function.

Activity

• No specific activity (comments, reviews, or progress updates) was provided in the context.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request re-enables two end-to-end tests by removing the @pytest.mark.skip decorator. While the change is straightforward, the pull request description is empty and the title has a typo ('skiped'). To align with the repository's style guide and improve clarity, I've suggested an updated title and a complete summary below. Please update the pull request accordingly.

Suggested PR Title:

[Test][BugFix] Re-enable skipped E2E tests

Suggested PR Summary:

### What this PR does / why we need it?

This PR re-enables two end-to-end tests that were previously skipped with a "fix me" reason:
- `test_models_aclgraph_capture_replay_metrics_dp2` in `tests/e2e/multicard/2-cards/test_aclgraph_capture_replay.py`
- `test_llama_lora` in `tests/e2e/singlecard/test_llama32_lora.py`

These tests were likely disabled temporarily and are now being re-activated, possibly due to fixes related to a vLLM version upgrade as indicated in the PR title.

### Does this PR introduce _any_ user-facing change?

No, this only affects the test suite.

### How was this patch tested?

The CI will run the re-enabled tests to verify they pass.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.