From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
dpdklab <dpdklab@iol.unh.edu>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] [dpdklab] Re: Community CI Meeting Minutes
Date: Tue, 7 Sep 2021 08:31:44 -0400 [thread overview]
Message-ID: <CAOE1vsP7MPNWiSY+CCpi5dkOHuK6R+7YJdozxhGSf+eSHmndag@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xa=s_oFy=ioo1WXRDfQipNY+TE_5XWb1w_nvCu-4eWLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hi David,
I've asked the guys to check on this.
Cheers,
Lincoln
On Tue, Sep 7, 2021 at 4:36 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Thu, Aug 26, 2021 at 3:34 PM Lincoln Lavoie <lylavoie@iol.unh.edu>
> wrote:
> > * Periodic ABI test for v20.11 is now enabled as part of LTS branch
> testing.
>
> Replying here, as I don't know if there is a separate thread on this topic.
>
> Looking at the dashboard history, I see the ABI test for ARM (v20.11
> tag) never passed successfully.
> The logs show:
> Error: reference directory
> '/opt/dpdklab/abi_references/"v20.11"/armgigabyteref' does not exist.
>
> It could be the extra double quotes, but in any case, please fix.
>
>
> --
> 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>
[-- Attachment #2: Type: text/html, Size: 2315 bytes --]
prev parent reply other threads:[~2021-09-07 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 13:33 [dpdk-ci] " Lincoln Lavoie
2021-08-26 16:05 ` Thomas Monjalon
2021-08-26 16:27 ` Lincoln Lavoie
2021-08-31 15:47 ` Thomas Monjalon
2021-09-01 12:49 ` Owen Hilyard
2021-09-07 9:23 ` Thomas Monjalon
2021-09-07 8:36 ` David Marchand
2021-09-07 12:31 ` 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=CAOE1vsP7MPNWiSY+CCpi5dkOHuK6R+7YJdozxhGSf+eSHmndag@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
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).