-
Notifications
You must be signed in to change notification settings - Fork 4k
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, native: uncaught exception in java.util.Logging #2576
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
platform: windows
type: bug
Milestone
Comments
@philwo : FYI |
laszlocsomor
added a commit
to laszlocsomor/bazel
that referenced
this issue
Sep 7, 2018
Fixes bazelbuild#6099 Fixes bazelbuild#6098 Related to bazelbuild#2576 Change-Id: Iabff91cca715d08e2977234e8615b2e0bf8a5dbc
bazel-io
pushed a commit
that referenced
this issue
Sep 7, 2018
laurentlb
pushed a commit
that referenced
this issue
Sep 10, 2018
laurentlb
pushed a commit
that referenced
this issue
Sep 10, 2018
laurentlb
pushed a commit
that referenced
this issue
Sep 12, 2018
laurentlb
pushed a commit
that referenced
this issue
Sep 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
platform: windows
type: bug
If you build Bazel with
--cpu=x64_windows_msvc
and run with--batch --output_user_base=c:\tmp3
, you'll see an uncaught exception:The problem is in
startup_options.cc
: we writejava.util.logging.FileHandler.pattern=c:\tmp3\l90hcebl/java.log
into thejavalog.properties
file and the\t
afterc:
is interpreted as a tab character. You can see that rendered in the error message too.The text was updated successfully, but these errors were encountered: