Tobias Werth
Tobias Werth
You can consider tweaking this flag: `--experimental_oom_more_eagerly_threshold`. Internally, we set it to 90.
huh, that's weird - it works for me on debian
Is this the right place to expose it? Most users likely don't care about CPU time. The idea behind `--experimental_stats_summary` is to provide the most useful information in a more...
Consider trying `--experimental_stats_summary` which will show a line like this: ``` INFO: 104 processes: 96 remote cache hit, 1 internal, 7 remote. ``` If you want to have the info...
In what cases is the distinction `remote`/`remote cache hit` as seen above not good enough?
We now have backwards incompatible change policy.
The general idea is to have all incompatible changes guarded behind flags. ErrorProne is not special in this.
I don't think we want to decouple. The main complaint (if I reread the comments correctly) is about breaking changes on every update. That shouldn't happen anymore.
That's a valid point about the technical simplicity, let me reopen this.
@philwo it would be great to have a progress bar. I was using the go version today and it took three minutes downloading the bazel binary on my connection (who...