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 completion returned by grpc_completion_queue) before starting a new read/write operation on that call (which is a violation of how gRPC's low level API should be used). On Sun, Aug 19, 2018 at 5:42 AM 'Srini Polavarapu' via grpc.io < grpc-io@googlegroups.com> wrote: > 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 crashes about 10/1000 times but only when run under bazel >> (i.e bazel test my_test). This happens with or without bazel sandboxing. >> >> When run on its own it works fine thousands of times. >> >> The most frequent test failure is >> >> E0817 19:54:09.499559477 18 server_cc.cc:629] Fatal: >> grpc_call_start_batch returned 8 >> E0817 19:54:09.499590418 18 server_cc.cc:630] ops[0]: >> SEND_INITIAL_METADATA(nil) >> E0817 19:54:09.499595057 18 server_cc.cc:630] ops[1]: >> SEND_MESSAGE ptr=0x2330f00 >> >> Sometimes I also see: >> E0817 19:54:21.345913273 18 proto_buffer_writer.h:65] assertion >> failed: !byte_buffer->Valid() >> >> Does this ring a bell for anyone? I did not find any similar issues >> reported so I thought I would ask here before I dig any deeper. >> >> I am using grpc v1.14.1, though the failure happens in a similar place >> even in 1.4.2 (from which I am upgrading our codebase). >> >> Thanks in advance. >> Abhishek >> > -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to grpc-io+unsubscr...@googlegroups.com. > To post to this group, send email to grpc-io@googlegroups.com. > Visit this group at https://groups.google.com/group/grpc-io. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/e775beeb-9600-45bf-bbdb-78eab5b4a725%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/e775beeb-9600-45bf-bbdb-78eab5b4a725%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Jan -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CACF4M0QOHypN6VyCu3-b0%3Dh2CLZpL8KOjHY1Tznys35XZu%2BwEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
