Skip to content
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, msysless: Bazel hangs if the server crashes early #2817

Closed
laszlocsomor opened this issue Apr 13, 2017 · 1 comment
Closed

Windows, msysless: Bazel hangs if the server crashes early #2817

laszlocsomor opened this issue Apr 13, 2017 · 1 comment
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) platform: windows type: bug

Comments

@laszlocsomor
Copy link
Contributor

laszlocsomor commented Apr 13, 2017

Description of the problem / feature request / question:

I added a ctor to WindowsFileSystem which just throws an exception.
The bazel client appears to hang:

C:\work\bazel>C:/tmp-cmd/o6hbs7n0/execroot/bazel/bazel-out/msvc_x64-fastbuild/bin/src/bazel.exe --output_user_root=c:\tmp9 build examples/cpp:hello-world
Extracting Bazel installation...
...............................................................................................................................................................................................................................................................................................................................................................................................^C

At the same time I see the exception in the jvm.out:

C:\work\bazel>type c:\tmp9\o6Hbs7N0\server\jvm.out
java.lang.IllegalStateException: DEBUG: WindowsFileSystem ctor
        at com.google.devtools.build.lib.windows.WindowsFileSystem.<init>(WindowsFileSystem.java:47)
        at com.google.devtools.build.lib.runtime.BlazeRuntime.fileSystemImplementation(BlazeRuntime.java:825)
        at com.google.devtools.build.lib.runtime.BlazeRuntime.newRuntime(BlazeRuntime.java:971)
        at com.google.devtools.build.lib.runtime.BlazeRuntime.createBlazeRPCServer(BlazeRuntime.java:850)
        at com.google.devtools.build.lib.runtime.BlazeRuntime.serverMain(BlazeRuntime.java:789)
        at com.google.devtools.build.lib.runtime.BlazeRuntime.main(BlazeRuntime.java:570)
        at com.google.devtools.build.lib.bazel.BazelMain.main(BazelMain.java:57)

Environment info

  • Operating System: Windows 10

  • If bazel info release returns "development version" or "(@non-git)", please tell us what source tree you compiled Bazel from; git commit hash is appreciated (git rev-parse HEAD):

C:\work\bazel>git rev-parse HEAD
8e042300d8e1eb6b9eda8a59bdb809aadb91d23b
  • the local modification to add the exception
@laszlocsomor laszlocsomor self-assigned this Apr 13, 2017
@laszlocsomor laszlocsomor added platform: windows P2 We'll consider working on this in future. (Assignee optional) type: bug labels Apr 13, 2017
@laszlocsomor
Copy link
Contributor Author

Ah. The culprit:

virtual bool IsStillAlive() { return true; }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) platform: windows type: bug
Projects
None yet
Development

No branches or pull requests

1 participant