test: verify periodic status-line refresh - #16039
Draft
Alizter wants to merge 1 commit into
Draft
Conversation
Alizter
force-pushed
the
status-line-refresh-regression
branch
from
August 18, 2026 13:10
7f23fef to
f2feb2a
Compare
Signed-off-by: Ali Caglayan <alizter@gmail.com>
Alizter
force-pushed
the
status-line-refresh-regression
branch
from
August 18, 2026 14:05
f2feb2a to
ab03794
Compare
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.
This is the regression-test commit for #16015, split out so the pre-fix behavior is visible independently while the test suite remains green.
The test starts a normal batch build whose action is blocked and silent. After the action starts, it records the current output offset, waits one second, and inspects only status output appended during that idle period. It requires two distinct duration values, excluding setup redraws and a single unrelated scheduler wakeup.
On
main, the expected output recordsbuild duration did not refresh repeatedly; the cram test therefore passes while demonstrating the existing behavior. The implementation commit in #16015 changes that expected output tobuild duration refreshed repeatedly.Verification:
./_boot/dune.exe runtest test/blackbox-tests/test-cases/status-line-refresh.t --forcepasses with the pre-fix output.