DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>,
	Thomas Monjalon <thomas@monjalon.net>,
	ci@dpdk.org, dev <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>,
	Aaron Conole <aconole@redhat.com>,
	Owen Hilyard <ohilyard@iol.unh.edu>
Subject: Re: [dpdk-dev] [dpdk-ci] [PATCH] version: 21.11-rc0
Date: Tue, 24 Aug 2021 08:19:52 -0400	[thread overview]
Message-ID: <CAOE1vsPjNY6qDxBSFOJR-juYw7yex3a2CkY_PJ-ha-hBW-_qCQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8w08LdznJA+BYTAYVXFupUej1tyoiSwK-bOtPYMvwkT=w@mail.gmail.com>

Hi David,

We'll check.  Owen was working on a change to allow ABI to still run for
merges onto the 20.11 branch, so the LTS branches can remain stable, while
per-patch testing is off for the 21.11 release.  Looks like that has a side
effect for how these patches were flagged in the system.

Cheers,
Lincoln

On Tue, Aug 24, 2021 at 3:58 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello Lincoln,
>
> On Tue, Aug 17, 2021 at 2:04 PM Lincoln Lavoie <lylavoie@iol.unh.edu>
> wrote:
> >
> > Hi David,
> >
> > ABI testing was disable / stopped on Friday in the Community CI lab.
> Patches from before that for 21.11 would have still had the test run and
> could have failures listed. I'm not sure if there is a way to "remove"
> those failure marks from patchworks.  But, for all new patches since then,
> ABI hasn't been run.
>
> I can see new reports for ABI, please can someone from UNH double check?
> https://lab.dpdk.org/results/dashboard/patchsets/18301/
> https://lab.dpdk.org/results/dashboard/patchsets/18303/
> https://lab.dpdk.org/results/dashboard/patchsets/18325/
>
>
> --
> David Marchand
>
>

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

      reply	other threads:[~2021-08-24 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 19:26 [dpdk-dev] " Thomas Monjalon
2021-08-12 14:36 ` Ferruh Yigit
2021-08-12 18:57   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-08-17  6:34 ` [dpdk-dev] " David Marchand
2021-08-17 12:04   ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
2021-08-17 15:19     ` David Marchand
2021-08-17 16:02       ` Ali Alnubani
2021-08-24  7:58     ` David Marchand
2021-08-24 12:19       ` 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=CAOE1vsPjNY6qDxBSFOJR-juYw7yex3a2CkY_PJ-ha-hBW-_qCQ@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=mdr@ashroe.eu \
    --cc=ohilyard@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).