From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: David Marchand <david.marchand@redhat.com>,
sys_stv <sys_stv@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Adrian Moreno Zapata <amorenoz@redhat.com>
Subject: Re: [dpdk-ci] CI error report
Date: Wed, 8 Jul 2020 01:27:50 +0000 [thread overview]
Message-ID: <MN2PR11MB4063563A83861128F5C656569C670@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8w21D0YR96crUTxo27b7aNoxr0xKKu5KjFT331q35-20Q@mail.gmail.com>
+1
Is there any way to update the CI result of below? I confirmed the base commit id
is wrong because of some CI errors.
http://mails.dpdk.org/archives/test-report/2020-July/142133.html
Thanks,
Chenbo
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, July 7, 2020 10:49 PM
> To: sys_stv <sys_stv@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Cc: ci@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Adrian Moreno Zapata
> <amorenoz@redhat.com>; Xia, Chenbo <chenbo.xia@intel.com>
> Subject: Re: [dpdk-ci] CI error report
>
> On Tue, Jul 7, 2020 at 4:14 PM David Marchand <david.marchand@redhat.com>
> wrote:
> >
> > On Tue, Jul 7, 2020 at 1:28 PM Xia, Chenbo <chenbo.xia@intel.com> wrote:
> > >
> > > Hi,
> > >
> > > I've observed some CI errors:
> > >
> > > http://mails.dpdk.org/archives/test-report/2020-July/141209.html
> > >
> > > This one has two failures both for make and meson. The first failure
> > > is caused by unrelated driver. The second one is in the related
> > > driver but unrelated code change.
> >
> > Intel CI is testing this patch against:
> >
> > DPDK git baseline: Repo:dpdk-next-virtio, CommitID:
> > 24cd1b529f35f106d323ebdd4df0203261824dcc
> >
> > Author: Ciara Power <ciara.power@intel.com>
> > Date: Thu Apr 30 17:01:37 2020 +0100
> >
> > doc: update telemetry guides
> >
> >
>
> Browsing through the test-report mailing list archive, this issue has been
> happening since Friday 07/03 and it got magically(?) fixed over the weekend.
> I still want an update on what was/is wrong and how it was/will be fixed.
>
> Thanks.
>
> --
> David Marchand
next prev parent reply other threads:[~2020-07-08 1:28 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
2020-07-07 14:14 ` David Marchand
2020-07-07 14:48 ` David Marchand
2020-07-08 1:27 ` Xia, Chenbo [this message]
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=MN2PR11MB4063563A83861128F5C656569C670@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=amorenoz@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=sys_stv@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).