I have increasingly been seeing issues like the following in the CI:
12:42:02 STEP: Performing Cilium preflight check
13:19:28 Sending interrupt signal to process
13:19:32 cleaning up VMs started for k8s tests
13:19:32
13:19:32 ---------------------------------------------------------
13:19:32 Received interrupt. Running AfterSuite...
13:19:32 ^C again to terminate immediately
13:19:34
13:19:34 Ran 45 of 297 Specs in 4082.881 seconds
That's a 40 minute gap between anything visible happening! Plus, to make things worse, we don't gather logs because the suite itself times out.
Something must be getting stuck in our code. Perhaps we can use some context.WithTimeout to handle these cases to debug this further?
I have increasingly been seeing issues like the following in the CI:
That's a 40 minute gap between anything visible happening! Plus, to make things worse, we don't gather logs because the suite itself times out.
Something must be getting stuck in our code. Perhaps we can use some
context.WithTimeoutto handle these cases to debug this further?