From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, sys_stv <sys_stv@intel.com>,
Aaron Conole <aconole@redhat.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Liang, LongfengX" <longfengx.liang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-ci] CI failing on dpdk-next-net-intel
Date: Thu, 10 Jun 2021 08:41:44 +0000 [thread overview]
Message-ID: <f33d5fad935a40b1a900b7f133a6e67c@intel.com> (raw)
In-Reply-To: <CAJFAV8zc3UtQGp4Zgj0rewz0_mOZF_oV3=5pXYEuP-QCPhgwBw@mail.gmail.com>
Sorry, It's our mistake, our repo is not updated.
> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of David Marchand
> Sent: 2021年6月10日 16:39
> To: Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Cc: ci@dpdk.org; sys_stv <sys_stv@intel.com>; Aaron Conole
> <aconole@redhat.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> Thomas Monjalon <thomas@monjalon.net>; Liang, LongfengX
> <longfengx.liang@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Subject: Re: [dpdk-ci] CI failing on dpdk-next-net-intel
>
> Cc: John.
>
> On Thu, Jun 10, 2021 at 10:17 AM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > On Thu, Jun 10, 2021 at 10:14 AM David Marchand
> > <david.marchand@redhat.com> wrote:
> > > Please, can Intel check their mirrors of next-net-* branches are up to date?
> >
> > This could explain the following bz too:
> > https://bugs.dpdk.org/show_bug.cgi?id=727
>
>
> --
> David Marchand
prev parent reply other threads:[~2021-06-10 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:14 David Marchand
2021-06-10 8:17 ` David Marchand
2021-06-10 8:39 ` David Marchand
2021-06-10 8:41 ` Tu, Lijuan [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=f33d5fad935a40b1a900b7f133a6e67c@intel.com \
--to=lijuan.tu@intel.com \
--cc=aconole@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=longfengx.liang@intel.com \
--cc=sys_stv@intel.com \
--cc=thomas@monjalon.net \
--cc=zhaoyan.chen@intel.com \
/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).