Increase e2e wait timeouts to reduce flakiness

[Okabe-Junya]

What

Raise wait timeouts in test/actions.github.com/helper.sh to reduce e2e flakiness. Each is overridable via an env var (defaults shown)

Why

(gha) E2E Tests is flaky on master (~half of recent push runs fail). The common cause is short, fixed timeouts on operations whose latency depends on the GitHub Actions service and runner startup. Each wait exits as soon as its condition is met, so raising the ceilings only helps slow cases and does not slow normal runs.

e.g.,

• https://github.com/actions/actions-runner-controller/actions/runs/28295070805/job/83833472985
• https://github.com/actions/actions-runner-controller/actions/runs/28295070805/job/83833472939
• https://github.com/actions/actions-runner-controller/actions/runs/24879052563/job/72842611455
• https://github.com/actions/actions-runner-controller/actions/runs/24409570716/job/71302303239

[Okabe-Junya]

not sure this PR will fix ALL flaky e2e tests, but let's see after merging

[Copilot]

Pull request overview

This PR aims to reduce flakiness in the Actions-hosted E2E workflow by increasing upper-bound wait limits in the E2E helper script, while keeping runs fast when conditions are met quickly.

Changes:

• Increase the scale set pod readiness wait timeout from 30s to 120s (env-overridable).
• Increase the autoscaling runner set cleanup wait timeout from 40s to 120s (env-overridable).
• Increase the workflow-run start wait budget from ~60s to ~180s by raising the retry ceiling (env-overridable).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[nikola-jokic]

Hey @Okabe-Junya,

We should start adding larger runner machines, but increasing test timeouts is still good if you ask me so we should merge this PR anyway ☺️ Thanks!

[Okabe-Junya]

Thank you!

We should start adding larger runner machines

Yes, would be nice to consider this! Can we use specialized machines (provided by the community or GitHub company) on github.com/actions? Or is it better to start with a large runner?