ci: keep PostgreSQL lanes on hosted runners - #737
Merged
Conversation
The managed Linux runners make PostgreSQL service-container tests much slower and cause the main PostgreSQL lane to time out. The same commit completes both lanes in minutes on GitHub-hosted runners. Keep these database-heavy jobs on GitHub-hosted Ubuntu until the managed Docker-in-Docker storage path is fixed. Hosted Go caching remains enabled because these jobs no longer use the fleet's persistent Go cache. Generated with Codex Co-authored-by: Codex <noreply@openai.com>
roborev: Combined Review (
|
wesm
added a commit
that referenced
this pull request
Sep 2, 2026
The new PostgreSQL shard matrix must follow the hosted-runner policy from #737. Running those service-container jobs on the managed fleet would retain the same slow Docker storage path that caused the original timeouts. Keep hosted Go caching enabled so each isolated shard job avoids a cold module and build cache. Generated with Codex Co-authored-by: Codex <noreply@openai.com>
wesm
added a commit
that referenced
this pull request
Sep 2, 2026
The new PostgreSQL shard matrix must follow the hosted-runner policy from #737. Running those service-container jobs on the managed fleet would retain the same slow Docker storage path that caused the original timeouts. Keep hosted Go caching enabled so each isolated shard job avoids a cold module and build cache. Generated with Codex Co-authored-by: Codex <noreply@openai.com>
wesm
added a commit
that referenced
this pull request
Sep 2, 2026
The managed Linux runners are about ten times slower than hosted Ubuntu for the Go test suite. On main the test job has hit go test's one-hour timeout in cmd/msgvault/cmd and internal/store in three of the last six runs, and on this branch the unsharded packages alone took 33 minutes there, followed by 20 minutes for the cmd/msgvault/cmd shards, during which a test that allows five seconds for a command to finish timed out. On hosted Ubuntu the same shards finish in under three minutes. The test and test-sharded jobs now run on hosted Ubuntu with Go caching, as #737 already did for the PostgreSQL lanes. The other Linux jobs stay on the managed runners. Generated with Claude Code Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PostgreSQL and pgvector lanes now always use GitHub-hosted Ubuntu, where the service-container tests complete in minutes instead of timing out on the managed Linux runners. Hosted Go caching stays enabled for both jobs; all other Linux jobs continue to use the managed runners.