Windows: clean --expunge fails

[abergmeier-dsfishlabs]

Description of the problem / feature request / question:

Executing bazel clean --expunge leads to:

INFO: Starting clean (this may take a while). Consider using --expunge_async if the clean takes more than several minutes.
ERROR: C:/tools/msys64/tmp/_bazel_a.bergmeier/dXgGrvqy/server/jvm.out (Permission denied).

Environment info

• Operating System: Windows 10
• Bazel version (output of bazel info release): 0.4.4

Have you found anything relevant by searching the web? (e.g. GitHub issues, email threads in the bazel-discuss@googlegroups.com archive)

Nope.

Anything else, information or logs or outputs that would be helpful?

Searching for server\jvm.out in Process Explorer gives two java.exe instances keeping a file handle (both seem to be A-servers). One is using it via C:\Users\a.bergmeier\AppData\Local\Temp and the other via C:\tools\msys64\tmp.

Should dXgGrvqy not contain hashed information about the Bazel version and change with each different Bazel binary used?

Currently it seems to always use dXgGrvqy, no matter which Bazel binary I am using.

[meteorcloudy]

Yes, this is an known issue. Related issues:
#1586 (comment)
#2077

[abergmeier-dsfishlabs]

Yes, this is an known issue. Related issues:
#1586 (comment)
#2077

Curious why issues were closed.

[abergmeier-dsfishlabs]

Searching for server\jvm.out in Process Explorer gives two java.exe instances keeping a file handle (both seem to be A-servers). One is using it via C:\Users\a.bergmeier\AppData\Local\Temp and the other via C:\tools\msys64\tmp.

Not related because happens with 1 running java.exe, too.

[Helcaraxan]

We have also observed this issue while trying out Windows builds.

[laszlocsomor]

Related bugs: #3043, #1906, #1586

[laszlocsomor]

70ff798 fixed this.