Lincoln Lavoie <lylavoie@iol.unh.edu> writes:
> As far as I can tell, it looks like one of the clocks fell out of sync on the container runners, which caused the
> builds to fail.
I think that's also been causing some failures with the alarm_test and
cycles_test unit tests. If the time source is making adjustments to
time, we will probably fail these tests as well.
> Also, as far I can tell from an initial look, it impacted the two patches Thomas cited. Two patches that are
> running now (i.e. they don't have a full set of results yet, look like they are running on. So, it was a transient
> issue. Obviously we need to track down its root cause. I suspect something happened with NTP, which should
> be keeping the runners and bare metal systems synced. I'm looking into that now.
>
> For the patches with the failed jobs, we will queue those for rerun today.
>
> Cheers,
> Lincoln
>
> On Wed, May 19, 2021 at 9:05 AM Aaron Conole <aconole@redhat.com> wrote:
>
> Thomas Monjalon <thomas@monjalon.net> writes:
>
> > It seems the IOL CI is failing today:
> >
> >
> https://patches.dpdk.org/project/dpdk/patch/1621406749-15536-1-git-send-email-changpeng.liu@intel.com/
>
> >
> https://patches.dpdk.org/project/dpdk/patch/20210519032745.707639-1-stevex.yang@intel.com/
>
> >
> > That's especially embarassing for closing the release.
>
> I don't see any useful logs in the failures.
>
> What changed?