[CI][ROCm] Raise AMD Model Executor shard timeout to 240m

[haic0]

Summary

• Set timeout_in_minutes: 240 on AMD Simple · Model Executor Test · Shard %N/%t jobs in ready and merge suites.
• Fixes build #12106-style failures where shards were killed at the implicit 120-minute Buildkite default during cold AITER JIT compilation (81 tests passed before timeout; no assertion failures).

Context

• Affected build: https://buildkite.com/vllm/vllm-omni-amd-ci/builds/12106
• PR [CI/Build][ROCm] Add distributed and tiny diffusion base GPU coverage #7605 ROCm jobs passed; only unrelated Model Executor shards timed out.

Test plan

• AMD ready CI picks up the new timeout on next build
• Model Executor shards complete within 240 minutes

AI assistance

AI assistance was used to diagnose the timeout and apply this CI-only change.

Signed-off-by: haic0 haic0@users.noreply.github.com

Made with Cursor

[vllm-omni-review-bot]

This PR was classified as CI work.

CI owner: @yenuo26 @congw729 @NickCao

Routing: @yenuo26 via semantic router, CI owner, CODEOWNERS; @congw729 via CODEOWNERS; @NickCao via CODEOWNERS

@haic0, please review your own changes and leave a short self-review comment describing what you checked. PRs without author self-review may not be assigned a reviewer.

Please take a look when you have a chance. If you would like an automated review, mention @vllm-omni-review-bot in a comment.

[vllm-omni-review-bot]

Omni ReviewBot: no human activity for 7 days

@haic0 this pull request has had no human commit, comment or review since 2026-09-17. Please confirm the current plan and next step. The author or a maintainer decides whether to change the PR state.

To keep it moving, any one of these is enough: push an update, reply to the open blocker, or post the current plan and timeline.

[vllm-omni-review-bot]

Omni ReviewBot: no human activity for 14 days

@haic0 this pull request has had no human commit, comment or review since 2026-09-17. Please consider marking this PR as draft until work can resume. The author or a maintainer decides whether to change the PR state.

To keep it moving, any one of these is enough: push an update, reply to the open blocker, or post the current plan and timeline.