[dpdk-dev] [dpdk-ci] dpdk-next-crypto/master is failing tests

Brandon Lo blo at iol.unh.edu
Thu May 20 17:30:32 CEST 2021


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 at redhat.com> wrote:
>
> On Thu, May 6, 2021 at 6:15 PM Brandon Lo <blo at 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 at iol.unh.edu

www.iol.unh.edu


More information about the dev mailing list