[CI/Build] Print running script to enhance CI log readability

[jeejeelee]

Some tests in CI involve executing Python scripts, making it difficult to quickly identify which script is causing failure. It is recommended to print script information before running such tests to help quickly locate the corresponding script.

@DarkLight1337

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[DarkLight1337]

We should use single quotes inside the yaml file since the content of this file is being expanded inside jinja template strings.

[jeejeelee]

The output meets the expectations of this PR, and the example test failure also shows that #10450 is not the reason

[youkaichao]

we should do it in the ci repo level , see vllm-project/buildkite-ci#52

[jeejeelee]

@youkaichao It looks like vllm-project/buildkite-ci#52 has implemented this functionality, right? If so, I will close this PR.

[youkaichao]

@youkaichao It looks like vllm-project/buildkite-ci#52 has implemented this functionality, right? If so, I will close this PR.

let me check for some ci jobs

[jeejeelee]

@youkaichao @DarkLight1337
It seems that merging this branch into forked main triggered an automatic merge. I apologize, I didn't notice this point.​​​​​​​​​​​​​​​​

[youkaichao]

no worry. i have reverted the change.