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>
Subject: Re: [dpdk-ci] UNH CI failing
Date: Wed, 19 May 2021 09:21:13 -0400
Message-ID: <CAOE1vsPeBtx+98AYdx3GDcPYStA7iSYUjEC6NaOfLuMCt5kjxQ@mail.gmail.com> (raw)
In-Reply-To: <f7tzgwqdgc6.fsf@redhat.com>

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

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.

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.


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
+1-603-674-2755 (m)

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

  reply	other threads:[~2021-05-19 13:21 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 [this message]
2021-05-19 15:54     ` Aaron Conole
2021-05-19 16:06       ` Lincoln Lavoie

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:

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

  git send-email \
    --in-reply-to=CAOE1vsPeBtx+98AYdx3GDcPYStA7iSYUjEC6NaOfLuMCt5kjxQ@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=thomas@monjalon.net \


* 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 \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

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