Julio Merino

@moroten Can you provide the exact warning you are seeing? As I mentioned earlier, I could not reproduce this...

Ah, found it. This comes from `TestResultAggregator.java`.

There are several kinds of data to be managed here: * Bazel "installation files". This is https://github.com/bazelbuild/bazel/issues/2109 and they should be auto-purged. No question. * Output trees. These are just...

Per #2765, one more thing to consider if implementing a smarter clean command is `bazel clean //target`. Noting here because this would possibly conflict with the `bazel clean some-id` proposal...

I just stumbled on this issue and would like to vote in favor of what @camillol is saying: Bazel created the garbage, so it's Bazel's responsibility to clean it up...

@jgavris The output base is different than the install base. The output base is specific to your project and you are responsible for getting rid of it via `bazel clean`...

I have an old design document that addressed this (which was internal only because it contained some non-public numbers IIRC). I didn't bother to externalize it because many of the...

Alright. I won't bother much with my proposal because it was rather long and wasn't well received. (The summary is that it was about creating lock files and using advisory...

I doubt this is a product question. The fact that this mentions "install" files doesn't mean it's an installation issue. Also, given that #1035 is very related to this and...

@sgowroji Please note that we (people outside of the Bazel org) don't have permissions to reopen issues. This is still a real usability problem that should be addressed. It may...