There's definitely something funny going on with the gem5art tests there but I believe that error is happening without triggering a non-zero exit code. The gem5art test script is set to `set -e`, which means the script should exit immediately after a failure, yet it doesn't. The testing also continues onto the other tests. I'll look into this.
In the example you linked, the issue appears to be because it has reached the 6 hour timeout. We could increase the timeout to fix this, but I'd like to know why our build/test times have increased enough to push us over the 6 hour line. I'll see if I can figure it out as well. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Jul 21, 2021 at 2:51 PM Gabe Black via gem5-dev <gem5-dev@gem5.org> wrote: > I've seen many kokoro failures lately, including this one which seems to > be from a problem in gem5-art? Any idea what's going on? > > > https://source.cloud.google.com/results/invocations/caae5aad-91a6-4c6e-9fbe-20962f9c5519/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
