From: Brandon Lo <blo@iol.unh.edu>
To: "Zhang, XuemingX" <xuemingx.zhang@intel.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
"Lilylavoie@iol.unh.edu" <Lilylavoie@iol.unh.edu>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"ci@dpdk.org" <ci@dpdk.org>, "Xu, Qian Q" <qian.q.xu@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dpdk-ci] iol-intel-performance did not send report after 9/3
Date: Thu, 10 Sep 2020 08:34:51 -0400 [thread overview]
Message-ID: <CAOeXdvZFyXrt4eMCsz3P67AUgNyKXnKkNbTjhmtePi17OX+h2g@mail.gmail.com> (raw)
In-Reply-To: <CY4PR11MB1624015034518103666A621986260@CY4PR11MB1624.namprd11.prod.outlook.com>
Hi Xueming,
Currently, we are in the process of adding additional functional tests
to the Niantic system.
I will get it back up and running soon; it will most likely be back up
by the end of today.
Thanks,
Brandon
On Tue, Sep 8, 2020 at 11:08 PM Zhang, XuemingX
<xuemingx.zhang@intel.com> wrote:
>
> Many thanks Brandon.
>
> We can receive reports, but only `fortville_spirit` has no `Niantic` results. Doesn't it run on Niantic?
> Could you help to check it?
>
> Eg: http://mails.dpdk.org/archives/test-report/2020-September/150285.html
>
> >-----Original Message-----
> >From: Brandon Lo <blo@iol.unh.edu>
> >Sent: Tuesday, September 8, 2020 11:24 PM
> >To: Zhang, XuemingX <xuemingx.zhang@intel.com>
> >Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>; david.marchand@redhat.com;
> >dpdklab@iol.unh.edu; Lilylavoie@iol.unh.edu; thomas@monjalon.net;
> >ci@dpdk.org; Xu, Qian Q <qian.q.xu@intel.com>; Tu, Lijuan
> ><lijuan.tu@intel.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; Ma,
> >LihongX <lihongx.ma@intel.com>
> >Subject: Re: iol-intel-performance did not send report after 9/3
> >
> >Hi Xueming,
> >
> >I have discovered the problem and am working on a solution.
> >Intel performance testing should be coming back up by today in patchworks.
> >
> >Thanks for letting me know,
> >Brandon
> >
> >On Tue, Sep 8, 2020 at 3:28 AM Zhang, XuemingX <xuemingx.zhang@intel.com>
> >wrote:
> >>
> >> Hi blo and all:
> >>
> >>
> >>
> >> Could you help to check the DPDK `ci/ iol-intel-performance`? No report
> >after 9/3.
> >>
> >>
> >>
> >> Thanks a lot!
> >>
> >>
> >>
> >> Regards,
> >>
> >> Xueming
> >>
> >>
> >
> >
> >
> >--
> >
> >Brandon Lo
> >
> >UNH InterOperability Laboratory
> >
> >21 Madbury Rd, Suite 100, Durham, NH 03824
> >
> >blo@iol.unh.edu
> >
> >www.iol.unh.edu
--
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:[~2020-09-10 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 7:27 Zhang, XuemingX
2020-09-08 15:24 ` Brandon Lo
2020-09-09 3:07 ` Zhang, XuemingX
2020-09-10 12:34 ` 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=CAOeXdvZFyXrt4eMCsz3P67AUgNyKXnKkNbTjhmtePi17OX+h2g@mail.gmail.com \
--to=blo@iol.unh.edu \
--cc=Lilylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=lihongx.ma@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=xuemingx.zhang@intel.com \
--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).