Repository navigation
fix(ci): align database refresh test deadlines with their job budgets - #456
Draft
PascaleBeier wants to merge 2 commits into
Draft
PascaleBeier wants to merge 2 commits into
PascaleBeier wants to merge 2 commits into
Conversation
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
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 November 1 DuckDB refresh failed after Go's implicit ten-minute package timeout, while its current test had run for only 21 seconds. The workflow already allows 45 minutes for the test step. Its AI-agent refresh path also runs the same database package under a longer outer step but inherits the same hidden Go deadline.
Adds an explicit 25-minute package deadline to both database-bearing refresh test commands. Preserves all packages, assertions, generators, schedules, branch selection, publication permissions and existing 30/45-minute step budgets.
Evidence: failed job https://github.com/HitKeep/hitkeep/actions/runs/41359487071/job/125006605741 reports
panic: test timed out after 10m0s, followed byFAIL hitkeep/database 600.130s. Current dependency qualification independently passed all three race shards and all 19 exhaustive migration cases; that result does not replace this workflow's own future refresh execution.Validation pending: canonical complete plan e3eed54d625e9a8d64066325 selects goreleaser-check, developer-docs, zizmor, actionlint and helm-lint; run 20261103T100332-89349ecb is active. Independent Ponytail/code review and required PR checks are pending. No data-refresh publication was triggered.