Skip to content

Give the CI tests job 60 minutes instead of 40 - #392

Merged
FujitsuPolycom merged 2 commits into
mainfrom
ci-tests-timeout
Nov 1, 2026
Merged

FujitsuPolycom merged 2 commits into
mainfrom
ci-tests-timeout

Conversation

@FujitsuPolycom

Copy link
Copy Markdown
Owner

Summary

Raises the tests job's limit in .github/workflows/ci.yml from 40 to 60 minutes.

Why: the job ran 26 to 39 minutes in the October 2026 runs. On 2026-10-31 the first run of #390 was stopped at the 40-minute limit with the suite at 98% and no failure; only a rerun passed, in 39 minutes. 60 minutes leaves room for slower runners and still ends a hung run.

Compatibility

CI only. No code or test changes; the other jobs' limits are unchanged.

Validation

The workflow parses as YAML; this PR's own CI run uses the new limit.

🤖 Generated with Claude Code

FujitsuPolycom and others added 2 commits October 31, 2026 21:25
The tests job ran for 26 to 39 minutes in the October 2026 runs. On
2026-10-31 a run of #390 was stopped at the 40-minute limit while the
suite was at 98% with no failure, and only a rerun passed (in 39
minutes). The limit is now 60 minutes, which leaves room for slower
runners while still ending a hung run.

Compatibility: CI only; no code or test changes.

Validation: the workflow parses as YAML. The other jobs' limits are
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@FujitsuPolycom
FujitsuPolycom merged commit b94a597 into main Nov 1, 2026
10 checks passed
@FujitsuPolycom
FujitsuPolycom deleted the ci-tests-timeout branch November 1, 2026 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant