From: Brandon Lo <blo@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Owen Hilyard <ohilyard@iol.unh.edu>, dev <dev@dpdk.org>,
ci@dpdk.org, Akhil Goyal <gakhil@marvell.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [dpdk-ci] dpdk-next-crypto/master is failing tests
Date: Thu, 20 May 2021 11:30:32 -0400 [thread overview]
Message-ID: <CAOeXdva0C5e=4DpH1DWHiZbYRDYSrSyO2G4V0HeOj3sJTyywpQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8z1rrsp0A=H9sP_f977HRcTqzPmRd9osBz5BbGCsfAOFA@mail.gmail.com>
Hi David,
Sorry for the late reply.
This may be due to the configuration with Jenkins on our side.
If I do not see that next-virtio and next-crypto are in Jenkins, I can
definitely add it in.
Thanks,
Brandon
On Tue, May 11, 2021 at 9:54 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Thu, May 6, 2021 at 6:15 PM Brandon Lo <blo@iol.unh.edu> wrote:
> >
> > Hi all,
> >
> > dpdk-next-qos and dpdk-next-pipeline remotes have been removed.
> > dpdk-next-virtio and dpdk-next-crypto remotes have been switched to
> > track main and for-main branches respectively.
>
> Thank you Brandon.
>
> Just an additional question.
>
> In the lab dashboard, I can find status/test reports for the most
> repositories, like main, next-net, next-net-intel.
> https://lab.dpdk.org/results/dashboard/tarballs/
>
> But I can't find next-virtio or next-crypto.
> Are they tested / supposed to land in this part of the dashboard?
>
>
> --
> David Marchand
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
prev parent reply other threads:[~2021-05-20 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 21:31 [dpdk-dev] " Owen Hilyard
2021-05-05 21:52 ` [dpdk-dev] [dpdk-ci] " Thomas Monjalon
2021-05-06 7:32 ` David Marchand
2021-05-06 16:14 ` Brandon Lo
2021-05-11 13:54 ` David Marchand
2021-05-20 15:30 ` Brandon Lo [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='CAOeXdva0C5e=4DpH1DWHiZbYRDYSrSyO2G4V0HeOj3sJTyywpQ@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).