Skip to content

Fix CI Standard Checks timeout due to runner restrictions#222

Merged
pannago merged 3 commits intomainfrom
PLT-3321
Apr 7, 2026
Merged

Fix CI Standard Checks timeout due to runner restrictions#222
pannago merged 3 commits intomainfrom
PLT-3321

Conversation

@pannago
Copy link
Copy Markdown
Contributor

@pannago pannago commented Apr 7, 2026

Fix CI Standard Checks timeout due to runner restrictions

Problem

CI Standard Checks workflow has been timing out after 24 hours since March 27. The reusable workflow defaults to ci-base-scale-set (self-hosted runners), but these are restricted to private repos. Public repos like .github can't access them, causing jobs to queue indefinitely until auto-cancelled.

Solution

Override the runner parameter to explicitly use ubuntu-latest (GitHub-hosted runners).

Changes

  • Updated .github/workflows/ci-standard-checks.yml to specify runner: ubuntu-latest

Impact

  • CI builds will now start immediately instead of timing out after 24 hours
  • Workflows will run on GitHub-hosted runners as intended for public repositories

Fixes: https://github.com/Typeform/.github/actions/runs/23858377425

pannago and others added 2 commits March 27, 2026 15:10
The CI Standard Checks workflow has been timing out after 24 hours
since March 27. The reusable workflow defaults to ci-base-scale-set
(self-hosted runners), which are restricted to private repos.

This change explicitly specifies ubuntu-latest (GitHub-hosted runners)
for this public repository.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pannago pannago requested a review from a team as a code owner April 7, 2026 10:27
@gitstream-cm
Copy link
Copy Markdown

gitstream-cm bot commented Apr 7, 2026

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

@gitstream-cm
Copy link
Copy Markdown

gitstream-cm bot commented Apr 7, 2026

🥷 Code experts: No results found

No code experts were identified for the files in this pull request based on git blame analysis.

This may occur when:

  • Files are new or have limited commit history
  • Git authors aren't mapped to current team members
  • Analysis thresholds need adjustment

If you expected to see expert suggestions, consider:

  • Reviewing your config.user_mapping settings

  • Adjusting the gt/lt parameters in your action

  • Verifying files have sufficient commit history

To learn more about /:\gitStream - Visit our Docs

@gitstream-cm
Copy link
Copy Markdown

gitstream-cm bot commented Apr 7, 2026

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

@gitstream-cm
Copy link
Copy Markdown

gitstream-cm bot commented Apr 7, 2026

🥷 Code experts: No results found

No code experts were identified for the files in this pull request based on git blame analysis.

This may occur when:

  • Files are new or have limited commit history
  • Git authors aren't mapped to current team members
  • Analysis thresholds need adjustment

If you expected to see expert suggestions, consider:

  • Reviewing your config.user_mapping settings

  • Adjusting the gt/lt parameters in your action

  • Verifying files have sufficient commit history

To learn more about /:\gitStream - Visit our Docs

@pannago pannago merged commit 7f4ebc2 into main Apr 7, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants