Yeah, I'm with you on your interpretation of that error.
I forgot a negation in my original reply to this email thread. I meant to
say I'm _not_ very confident in the wait solution, and the more I think it
through, I'm even less so, as the error occurs after the docker image is
pulled, so I'd
Yeah, I'm hesitant to blame the docker image too, since as far as I know it
hasn't really changed much recently, and this problem has only really
started recently, although I've hit it a lot in the last few days. Some
sort of timing issue seems like a reasonable hypothesis. Could you please
add
Correction: The command is "sleep", not "wait" :).
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616
web: https://www.bobbybruce.net
On Tue, May 25, 2021 at 9:46 AM Bobby Bruce wrote:
> It is annoying when this happens, and doubly so that it's clearly flakey
> and hard
It is annoying when this happens, and doubly so that it's clearly flakey
and hard to reproduce. However, I've only ever seen this on Kokoro so I
think the blame is somewhere there. Keep in mind, we run nightly tests
using the same image and never seem to run into this issue, I'm quite
confident
