[6.0.0] Remove logic that increases delay between progress updates over time #16606
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.
Removes a bit of undocumented behavior that increases the delay between progress updates the longer the build is running. Potentially resolves #16119
Also renamed
MAXIMAL_UPDATE_DELAY_MILLIS
toMINIMAL_UPDATE_INTERVAL_MILLIS
because it is used as a minimum and doesn't affect the delay between messages.Fixes #16119.
Closes #16221.
RELNOTES[INC]: Bazel no longer increases the delay between progress updates when there is no cursor control.
PiperOrigin-RevId: 484203851
Change-Id: I33f7302ca85b75135744eb6093b618196199a49f