1.2.0: TestServerInterceptorSuite failures #56
Comments
Problem is easy enough to reproduce by running tests repeatedly. Usually it only takes 2...15 tries before this test fail. I could not reproduce after applying the following patch:
|
I'm fine with bumping the timeout in the tests as there are actual servers being started here, so there could be various things that could cause some delay. What do you think @Bplotka? |
We've got some feedback from autobuilders and unfortunately changing this timeout turned out to be ineffective... Even though adjusting timeout changed outcome in my environment, on autobuilders this test still fails reliably and reproducibly... No ideas why... :( |
In that case and since it’s relatively easy to reproduce I think we should record cpu and mutex/lock profiles and see if there is anything we can do. (If it’s syscalls then there is little we can so, but it’s worth trying I think) |
Yea, we cannot bump timeouts indefinitely. And CI tends to be slow. We need some other solution to this. |
Alternative approach would be to add |
How running same test 20 time halps for this issue? |
As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902466
TestServerInterceptorSuite
sometimes fails as follows:https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/golang-github-grpc-ecosystem-go-grpc-prometheus.html
The text was updated successfully, but these errors were encountered: