Julio Merino

@kastiglione All outputs (except for top-level ones) are inputs to other actions. Bazel needs to know if they have been modified out-of-band to invalidate their corresponding actions. (Yes, you could...

I'm not sure why you focus on fseventsd though... That's probably a symptom more than a problem. What exactly are you doing? What build times are you seeing? What are...

Also... the only thing left to try is to run with `--sandbox_debug` to keep the sandbox directory around, run with `--subcommands` to print what is being run, and then manually...

Aha, yeah, that explains it (or at least one problem). I had encountered this earlier because the way the module cache works breaks loudly when sandboxfs is in use but...

@allevato We'd easily poke a hole in the sandbox to share a cache across actions. Sure, mumble mumble sandboxing, but if the performance hit is so significant, and if it...

Interesting and, ugh, incomplete error messages that don't say *why* things failed. How often do you hit this though? Seems like quite a corner case.

Sure. We'd need to define the API though. Looking at QB64, I see https://qb64.com/wiki/TIME$.html (which should be added but isn't quite the same as you want) and https://qb64.com/wiki/TIMER-(statement).html (which is...

Another thought that came to mind: maybe it's *the toolchain* definition what should be able to supply the memory model for the linker and compiler. I'm not sure if this...

That's a good idea. I modified `CppLinkAction` to capture the size of the inputs along with the counts, made it dump metrics to the log, and graphed the results. The...

@larsrc-google No, I did not. I do not think our build or link actions are sufficiently large to gather any meaningful performance data of this change (other than seeing no...