Re: [grpc-io] Re: Fatal: grpc_call_start_batch returned 8

2018-08-19 Thread 'Jan Tattermusch' via grpc.io
FTR, it looks like "grpc_call_start_batch returned 8" corresponds to: /** there is already an outstanding read/write operation on the call */ GRPC_CALL_ERROR_TOO_MANY_OPERATIONS, That may mean that for a given call, you are not waiting for outstanding read/write operations to finish (the tag comp

[grpc-io] Re: Fatal: grpc_call_start_batch returned 8

2018-08-18 Thread 'Srini Polavarapu' via grpc.io
There is some flakiness in bazel tests. Please file an issue on github and provide the steps in detail to reproduce this. Thanks. On Friday, August 17, 2018 at 3:16:13 PM UTC-7, Abhishek Parmar wrote: > > I have a weird problem with one of my unit tests that is using streaming > grpc. The test