-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: output_root default should not be in TMP #5038
Labels
Comments
laszlocsomor
added
type: bug
P0
This is an emergency and more important than other current work. (Assignee required)
platform: windows
release blocker
labels
Apr 17, 2018
Blocking #4583. |
laszlocsomor
added
P1
I'll work on this now. (Assignee required)
and removed
P0
This is an emergency and more important than other current work. (Assignee required)
labels
Apr 17, 2018
OK, P0 was too much:
P1 though because it is bad enough. |
laszlocsomor
added a commit
to laszlocsomor/bazel
that referenced
this issue
Apr 17, 2018
This is an immediate fix for a very nasty bug: bazelbuild#5038 Change-Id: I5e4f9fa13e5ac785514bc0dc4ce6cba9a88f33bb
This was referenced May 15, 2018
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
Read bazelbuild/continuous-integration#252 (comment) and following 5 comments.
TL;DR: If anything deletes your $TMP that's not aware of junctions and your outputroot is under the $TMP, then the external repo junctions and every junction pointing to places all over the filesystem will have files deleted from them.
Immediate solution: use GetHomeDir() instead of
$TMP
.What operating system are you running Bazel on?
All windows versions.
What's the output of
bazel info release
?0.12.0
Have you found anything relevant by searching the web?
Related: bazelbuild/continuous-integration#252
The text was updated successfully, but these errors were encountered: