Tom Cnops

Regarding the build failures: it appears to me that the failing `//src/test/java/com/google/devtools/build/lib/remote:remote` doesn't touch the code I changed (it passess locally when I put `System.exit(1)` in the removed if-branch). But...

I read that as well, but I don't see how it still applies. There now is `--show_progress_rate_limit` to set a minimum delay between updates and `--progress_report_interval` to set the scheduled...

If no flags are provided, the default is interval is 20 seconds. So for the first ~2 minutes (20/0.15 seconds), there is no difference in output with and without this...

When updating the docs I noticed that `progress_report_interval` is actually used by the [ActionExecutionStatusReporter](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporter.java#L261), and not by the `UiEventHandler`. The `UiEventHandler` used a hardcoded limit (1 second if there is...

Yes, the `ActionExecutionStatusReporter` is not impacted by curses-ness, so it will always fire progress events on the `progress_report_interval` (or 10/30/60/60 ... if it is 0). In addition to that, the...

Hi @sgowroji, I updated the original post. The minimal example can also be found at at https://github.com/tom-cnops/progress-minimal-example. Running `bazel test //:sleep_test --progress_report_interval=2 2> output.txt` writes to the output file like...

As far as I can see `show_progress_rate_limit` does indeed set a _minimum_ time. The docs could perhaps be formulated a bit better, but they also seem to suggest a minimum...