From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Ali Alnubani <alialnu@mellanox.com>, "ci@dpdk.org" <ci@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Brandon Lo <blo@iol.unh.edu>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] CI error report
Date: Tue, 7 Jul 2020 11:35:48 +0000 [thread overview]
Message-ID: <MN2PR11MB4063251E6691054955F300149C660@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VI1PR05MB44146924F5205180942EB671D7660@VI1PR05MB4414.eurprd05.prod.outlook.com>
Thanks, Ali!
I will keep an eye on the status.
BRs,
Chenbo
> -----Original Message-----
> From: Ali Alnubani <alialnu@mellanox.com>
> Sent: Tuesday, July 7, 2020 7:33 PM
> To: Xia, Chenbo <chenbo.xia@intel.com>; ci@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Brandon Lo <blo@iol.unh.edu>;
> dpdklab@iol.unh.edu
> Subject: RE: CI error report
>
> Hi Xia,
>
> > -----Original Message-----
> > From: ci <ci-bounces@dpdk.org> On Behalf Of Xia, Chenbo
> > Sent: Tuesday, July 7, 2020 2:28 PM
> > To: ci@dpdk.org
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>
> > Subject: [dpdk-ci] CI error report
> >
> [snip]
> >
> > This one fails on iol-mellanox-Performance, and AFAIK this test should
> > not run the patch's code.
> >
>
> This is a test issue, and I noticed that Brandon is already re running it.
>
> Regards,
> Ali
next prev parent reply other threads:[~2020-07-07 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 11:28 Xia, Chenbo
2020-07-07 11:33 ` Ali Alnubani
2020-07-07 11:35 ` Xia, Chenbo [this message]
2020-07-07 14:14 ` David Marchand
2020-07-07 14:48 ` David Marchand
2020-07-08 1:27 ` Xia, Chenbo
2020-07-08 1:38 ` Chen, Zhaoyan
2020-07-08 1:44 ` Ma, LihongX
2020-07-08 2:11 ` Xia, Chenbo
2020-07-08 2:52 ` Ma, LihongX
2020-07-08 2:55 ` Xia, Chenbo
2020-07-08 5:45 ` David Marchand
2020-07-08 8:17 ` Chen, Zhaoyan
2020-07-08 11:25 ` David Marchand
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=MN2PR11MB4063251E6691054955F300149C660@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=alialnu@mellanox.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@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).