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 the images are good..
I'm very confident in this theory, but we do stop and start the Docker service just before running the docker command (in `tests/jenkins/presubmit.sh`). It could be the Jenkins service is still figuring stuff out and needs a few more nanoseconds before we jump in and booting a container. We could put a "wait 5" between starting the service and running our tests to see if that helps. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon, May 24, 2021 at 11:21 PM Gabe Black via gem5-dev <gem5-dev@gem5.org> wrote: > Hi folks. I've noticed kokoro runs occasionally failing with: > > bash: : command not found > > This is after the docker command runs it looks like, so I'm assuming this > is a problem with our docker image? Any ideas? > > > https://source.cloud.google.com/results/invocations/563a3724-49d8-4136-b30f-e19f85db8332/targets/gem5%2Fgcp_ubuntu%2Fpresubmit/log > _______________________________________________ > gem5-dev mailing list -- gem5-dev@gem5.org > To unsubscribe send an email to gem5-dev-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
