Windows, Bazel 0.17.0rc2, regression: bazel no longer writes java.log

[laszlocsomor]

Description of the problem / feature request:

0.17.0 rc2 regression over rc1: Bazel on Windows no longer writes <output_base>/java.log.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Build anything with 0.17.0 rc1, then run bazel info output_base, list the reported directory, see java.log is there.
Do the same with rc2, see that java.log is not there.

What operating system are you running Bazel on?

Windows 10 v1709

[laszlocsomor]

I found the root cause: similarly to #2576, it's the java log path. Turns out we must pass the path with escaped backslashes instead of forward slashes. Working on a fix.

[lberki]

How come it worked in 0.17rc1 then?

[laszlocsomor]

I don't know yet. What I do know is that (a) the fix solves this issue, and (b) the fix removes an exception from the <output_base>/server/jvm.out that I've been aware of for a long time, but which never seemed to result in any problems (until now?).