Repository navigation
The required CI check runs close to its 30-minute limit #837
Description
Summary
ci / Build and test (added in #836, datum-cloud/infra#8399) builds the operator and runs its envtest suite in about 23 minutes. The shared ci-basic workflow it calls stops a job at 30 minutes. Once the check is required, a slow runner or a slightly bigger suite times it out, and every pull request here is blocked from merging until someone re-runs it.
Done when
- The required check finishes well inside its limit (under 15 minutes on a normal run). Options: run only the unit packages in the required check and keep the long envtest packages in the existing Tests workflow, or split the suite across parallel non-matrix jobs behind one required roll-up.
- Or the check's timeout is raised in datum-cloud/actions with a recorded reason, if the suite can't get faster
Related to datum-cloud/infra#8399
Activity
vvoytovych commentedon Nov 3, 2026
The nearer limit is the test binary's own:
ci.yamlrunsgo test -timeout 20m, which stopsinternal/controllerat 1200 s. Onmainthat package took 1131–1170 s in this check (for example run 41550441598) and 1036–1160 s in Tests. #844 hit it: its job stopped withtest timed out after 20m0s, while Tests passed the same package in 1132 s. So the split or a longer limit is needed for that package as well as for the job.ci: Give the test run Go's default timeout again
vvoytovych commentedon Nov 5, 2026
The required check now finishes well inside its limit, so this is done. The end-to-end workflows continue in #867.
Each criterion, read against every green run on
mainfrom #848's merge to #863's (2026-11-04 15:03Z to 2026-11-05 10:02Z):These changes did it:
make test-suite, with envtest's versions fromgo.mod