DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Aaron Conole <aconole@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-ci] UNH CI failing
Date: Wed, 19 May 2021 12:06:35 -0400
Message-ID: <CAOE1vsMaoeNiXaV5CuZJcf5Q39LJHmdFbHq=Daed9vXAxDJdgg@mail.gmail.com> (raw)
In-Reply-To: <f7tsg2ibtxw.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2780 bytes --]

I'm continuing to hunt. I did confirm all of those systems are syncing time
from the same master, using chronyd, and look to be configured correctly.
I'm not sure what would cause the time to jump like that, unless maybe the
"master", which is our IPA server, synced it's time and that caused some
sort of ripple to the downstream other systems.

The patches have been rerun, with most results coming in,
https://lab.dpdk.org/results/dashboard/patchsets/17130/, and are passing
without issue.

The only failures I see in recent patches are on "bugfix for Kunpeng SVE
compile" (https://lab.dpdk.org/results/dashboard/patchsets/17135/), with
unit tests failing on two OSes.

And the intermittent Dynamic Config failure.  We think we have tracked this
down to a patch we sent into DTS, and that was merged into DTS, but was
then reverted a few days ago (
https://git.dpdk.org/tools/dts/commit/?id=90f460df240b3020191916b15705abe208a14694).
I've asked Lijuan why it was reverted.

Cheers,
Lincoln

On Wed, May 19, 2021 at 11:55 AM Aaron Conole <aconole@redhat.com> wrote:

> 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?
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 5267 bytes --]

      reply	other threads:[~2021-05-19 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  7:36 Thomas Monjalon
2021-05-19 13:05 ` Aaron Conole
2021-05-19 13:21   ` Lincoln Lavoie
2021-05-19 15:54     ` Aaron Conole
2021-05-19 16:06       ` Lincoln Lavoie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOE1vsMaoeNiXaV5CuZJcf5Q39LJHmdFbHq=Daed9vXAxDJdgg@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ https://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git