You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bazel crashed while unable to write to stdout. I would expect Bazel to close with an error instead of crashing, as the crashing behavior clears the analysis cache.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I reproduced it by piping an acquery call to a jq pipeline that failed with a syntax error.
Any other information, logs, or outputs that you want to share?
jq: error: syntax error, unexpected '[', expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at <top-level>, line 1:
. | [ .actions.[].outputIds[] ]
jq: error: syntax error, unexpected ']', expecting $end (Unix shell quoting issues?) at <top-level>, line 1:
. | [ .actions.[].outputIds[] ]
jq: 2 compile errors
Starting local Bazel server and connecting to it...
INFO: Invocation ID: bdb56bbe-1ed6-4078-a9f3-7430635415f6
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
<SNIP>
INFO: Found 1 target...
INFO: Deleting stale sandbox base /private/var/tmp/_bazel_jhoward/6629d7ad2e07b93af304e686ea085d2a/sandbox
Cannot write to standard output; exiting...
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.AssertionError
at com.google.devtools.build.lib.remote.ReferenceCountedChannel$1.deallocate(ReferenceCountedChannel.java:48)
at io.netty.util.AbstractReferenceCounted.handleRelease(AbstractReferenceCounted.java:86)
at io.netty.util.AbstractReferenceCounted.release(AbstractReferenceCounted.java:76)
at com.google.devtools.build.lib.remote.ReferenceCountedChannel.release(ReferenceCountedChannel.java:144)
at com.google.devtools.build.lib.remote.GrpcCacheClient.close(GrpcCacheClient.java:166)
at com.google.devtools.build.lib.remote.disk.DiskAndRemoteCacheClient.close(DiskAndRemoteCacheClient.java:64)
at com.google.devtools.build.lib.remote.RemoteCache.close(RemoteCache.java:1021)
at com.google.devtools.build.lib.remote.RemoteActionContextProvider.executionPhaseEnding(RemoteActionContextProvider.java:154)
at com.google.devtools.build.lib.buildtool.ExecutionTool.shutdown(ExecutionTool.java:229)
at com.google.devtools.build.lib.buildtool.BuildTool.buildTargets(BuildTool.java:245)
at com.google.devtools.build.lib.buildtool.BuildTool.processRequest(BuildTool.java:408)
at com.google.devtools.build.lib.runtime.commands.AqueryCommand.exec(AqueryCommand.java:136)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.execExclusively(BlazeCommandDispatcher.java:579)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.exec(BlazeCommandDispatcher.java:231)
at com.google.devtools.build.lib.server.GrpcServerImpl.executeCommand(GrpcServerImpl.java:543)
at com.google.devtools.build.lib.server.GrpcServerImpl.lambda$run$1(GrpcServerImpl.java:606)
at io.grpc.Context$1.run(Context.java:579)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException
at com.google.devtools.build.lib.remote.grpc.ChannelConnectionFactory$ChannelConnection.close(ChannelConnectionFactory.java:56)
at com.google.devtools.build.lib.remote.grpc.SharedConnectionFactory.close(SharedConnectionFactory.java:75)
at com.google.devtools.build.lib.remote.grpc.DynamicConnectionPool.close(DynamicConnectionPool.java:57)
at com.google.devtools.build.lib.remote.ReferenceCountedChannel$1.deallocate(ReferenceCountedChannel.java:46)
... 19 more
Caused by: java.lang.InterruptedException
at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(Unknown Source)
at java.base/java.util.concurrent.CountDownLatch.await(Unknown Source)
at io.grpc.internal.ManagedChannelImpl.awaitTermination(ManagedChannelImpl.java:861)
at io.grpc.internal.ForwardingManagedChannel.awaitTermination(ForwardingManagedChannel.java:57)
at com.google.devtools.build.lib.remote.grpc.ChannelConnectionFactory$ChannelConnection.close(ChannelConnectionFactory.java:54)
... 22 more
The text was updated successfully, but these errors were encountered:
Description of the problem / feature request:
Bazel crashed while unable to write to stdout. I would expect Bazel to close with an error instead of crashing, as the crashing behavior clears the analysis cache.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I reproduced it by piping an
acquery
call to ajq
pipeline that failed with a syntax error.What operating system are you running Bazel on?
What's the output of
bazel info release
?Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: