Fix the path to the testing script.

[QiliangCui]

Fixing a test case and testing by following the instruction in https://github.com/vllm-project/ci-infra?tab=readme-ov-file#how-to-onboard-runners-onto-ci-cluster-on-buildkite

[github-actions]

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Summary of Changes

Hello @QiliangCui, 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 resolves an issue where the incorrect benchmark script was being executed during TPU testing. It updates the script path within the Docker container setup to correctly point to the TPU-specific benchmark script, ensuring that the intended tests are run as expected and aligning with the stated goal of fixing a test case.

Highlights

• Path Correction: Corrected the path to the benchmark execution script within the docker_run_bm.sh script. The path was updated from .buildkite/scripts/hardware_ci/run_bm.sh to .buildkite/scripts/tpu/run_bm.sh, ensuring the correct TPU-specific benchmark script is invoked inside the Docker container.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 fixes a broken path to a test script in a CI pipeline. I've added one suggestion to make the script path dynamic, which would improve the long-term maintainability of the CI script.

[gemini-code-assist]

The path to run_bm.sh is hardcoded. For improved maintainability, construct the path dynamically. This makes the script more robust if the directory is moved or renamed in the future.

Suggested change

	docker exec "$CONTAINER_NAME" /bin/bash -c ".buildkite/scripts/tpu/run_bm.sh"
	docker exec "$CONTAINER_NAME" /bin/bash -c "$(dirname \"${BASH_SOURCE[0]}\")/run_bm.sh"