Repository navigation
ci(oceanbase): budget isolated long-query acceptance - #2211
Merged
hidb4ai merged 1 commit intoOct 23, 2026
Conversation
Allow complete Server setup within the aggregate long-query CI step. Eight healthy isolated cases can exceed the former ten-minute limit while each remains inside the existing three-minute process deadline. Constraint: Keep all assertions, the 180-second case limit and the 100-minute job limit. Scope-risk: CI aggregate execution budget only; runtime and migration resources are unchanged. Tested: Eight real OceanBase cases passed without skips in 665.9 seconds; YAML structure and git diff --check pass; Ty and other validators pass in the existing environment, while the hook wrapper reports JSON normalizations without a tracked JSON diff.
hidb4ai
merged commit Oct 23, 2026
0b1d6f3
into
oceanbase:codex/issue-2154-full-server-upgrade
86 of 88 checks passed
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.
Which issue or RFC does this PR close?
Refs #2084 and #2168. This PR targets the full Server upgrade branch because its complete Server fixtures expose the aggregate timeout. The patch is published from AlexStocks' fork for the target author to review and integrate.
Rationale for this change
The OceanBase clean migration job can pass healthy isolated cases but be killed before the full long-query suite finishes. Job 120359936089 passed all 47 migration cases, then reached the long-query step's ten-minute limit. Its artifact contains seven passing long-query reports and no completed eighth result.
A real OceanBase diagnostic measures approximately 81 seconds of complete Server setup, 5.3 seconds of startup, and 1.1 seconds across the four HTTP requests in one case. The isolated runner grants each case 180 seconds; all eight cases plus collection can exceed the aggregate ten-minute budget while respecting those individual bounds.
What changes are included in this PR?
Increase only this step's aggregate timeout from 10 to 30 minutes, allowing eight 180-second cases plus bounded collection and process cleanup. Retain the runner's per-case timeout, all assertions, stop-on-failure behavior and the job's 100-minute outer limit.
Are there any user-facing changes?
CI execution budget only.
How was this change tested?
scripts/run_atomic_memory_clean_migration.py oceanbase --tests tests/e2e/test_atomic_artifact_search_http.py tests/e2e/test_atomic_memory_long_fts_query.pyagainst an isolated real OceanBase instance: 8 passed, zero failures/errors/skips, in 665.9 seconds, exceeding the former 600-second aggregate deadline.git diff --checkand YAML validation pass.UV_NO_SYNC=1 prek run -aexecutes Ty and the other validators successfully but exits 1 becausepretty-format-jsonreports normalizations; the tracked diff still contains only this YAML change. A full hook pass is not claimed. The ordinary invocation separately encounters editable-package VCS discovery failure through the Windows worktree under WSL.AI usage statement
Implemented and validated with OpenAI Codex under maintainer direction.