Repository navigation
Fix waiting-line configuration for Process and Review runs - #2005
Merged
Merged
Conversation
Open
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.
Summary
Process and Review runs now honor
logs.waiting_line_minutesand the half-silence fallback. Their startup paths already configure logging but bypassed the two entry points that initialized waiting lines, leaving a five-minute default.Remove the redundant initialization calls in Ticket and Experiment startup; retain test-minute scaling unchanged.
Closes #1983
Evidence
Execution evidence
d7f9f184,cargo test --test ci custom_process_ci_waiting_lines_use_the_configured_interval -- --exact --nocapturefailed:expected repeated CI waiting lines, got 1;0 passed; 1 failed. The copied ticket-run Custom process completed successfully after 14 pending CI observations withlogs.waiting_line_minutes = 1andTHIRDSHIFT_WAITING_MINUTE_MS=150.After: The same command passed:
1 passed; 0 failed. Centralizing initialization confirms the startup gap as the cause.--author, Custom process issue startup, and Process Pass/issue host-resource waits. Both explicit intervals and the half-silence fallback repeat lines on stderr with matching counts in the Command log. Existing Ticket and Self-merge heartbeat checks also pass.CARGO_BUILD_JOBS=2 RUST_TEST_THREADS=3 /usr/bin/time -p scripts/affected-tests refs/remotes/origin/mainpassed:PASS cargo test (4444.68s). Compilation is included; Nextest was unavailable, so the selector used its documentedcargo testfallback with three test threads.c9fa1a38,CARGO_BUILD_JOBS=2 RUST_TEST_THREADS=3 cargo test --test ci waiting_lines -- --nocapturepassed all three selected tests.cargo fmt --checkand CI also passed, including site and Console checks and both Linux artifact builds.Seams under test
Review coverage
Unaddressed findings
Security review outcome
No unaddressed introduced findings.
Merge Danger
Door: two-way
Blast Radius: logging
Waiting stages now initialize their existing interval at the common logging startup seam. No persistent-data change.
Built with codex codex-cli 0.167.1 · gpt-6.1-sol · xhigh