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

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


  parent reply	other threads:[~2021-08-24  7:58 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 [this message]
2021-08-24 12:19       ` 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:
  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='CAJFAV8w08LdznJA+BYTAYVXFupUej1tyoiSwK-bOtPYMvwkT=w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=mdr@ashroe.eu \
    --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).