[AMD Public Use]
Hi Gabe,
We are seeing similar errors, so +1 priority on this. Some of our changes that
where ready to submit got rerun (for some reason?) and then failed with the
same error. My (weak) theory is that maybe it has something to do with how it
is checking for timeouts and maybe
I'm 95% sure I've just fixed this. The problem was due to me failing to
include the aarch-system-20200611.tar.bz tarball on our Google Cloud when
releasing v21.0. Kokoro downloads this to run certain arm tests. If it
can't download this tarball the tests fail (I need to get round to
improving this
Hi Gabe,
Apologies for the late reply; I was on vacation.
That is not a "problem" in testlib. It happens when regressions are aborted by
external forces (e.g. a timeout in Jenkins/kokoro); then the time field
of metadata doesn't get populated.
We should probably fix this by initializing time to
Yep, that would be great. Thanks!
Gabe
On Wed, Mar 31, 2021 at 1:27 AM Giacomo Travaglini <
giacomo.travagl...@arm.com> wrote:
> Hi Gabe,
>
> Apologies for the late reply; I was on vacation.
> That is not a "problem" in testlib. It happens when regressions are
> aborted by external forces (e.g.
