see this. While investigating to see if the background workers add any performance gains after updating rules to follow the worker protocol protocol (see #54) I disovered that compiling erroneous code in error mode from a persistent workers leads to:
---8<---8<--- Start of log, file at /private/var/tmp/_bazel_hassan/b35d318b00182129bd971b30e0d6ece1/bazel-workers/worker-4-KotlinCompile.log ---8<---8<---
(empty)
---8<---8<--- End of log ---8<---8<---
INFO: Elapsed time: 8.683s, Critical Path: 7.58s
The compiler processes seem to write to stdout / stderr instead of log files that Bazel allocates. This doesn't work for the intellij plugin or when the process is in background mode.
see this. While investigating to see if the background workers add any performance gains after updating rules to follow the worker protocol protocol (see #54) I disovered that compiling erroneous code in error mode from a persistent workers leads to:
The compiler processes seem to write to stdout / stderr instead of log files that Bazel allocates. This doesn't work for the intellij plugin or when the process is in background mode.