From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, XuemingX" <xuemingx.zhang@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
"ci@dpdk.org" <ci@dpdk.org>,
ferruh.yigit@intel.com, john.mcnamara@intel.com,
tim.odriscoll@intel.com, aconole@redhat.com
Subject: Re: [dpdk-ci] Intel CI reports
Date: Fri, 10 Jan 2020 14:07:51 +0100 [thread overview]
Message-ID: <2479331.KRxA6XjA2N@xps> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E4072D32E@shsmsx102.ccr.corp.intel.com>
General comment about Intel CI below.
First, let me say thanks because during years Intel was the company
doing some community CI effort.
Second, I think the maintenance of this CI should be more serious
in order to make it reliable.
Few examples:
- here we have a fail with a success result
- recently the CI was failing during weeks without anybody
monitoring and noticing the issue
- quite often, some changes are done in the platforms
without making sure it still works
Please could you take actions to make sure such issue won't happen anymore?
As the first in the game, Intel should be a good example
to give confidence in the CI in general, and to show the example
to other companies to make the same.
Thanks
10/01/2020 12:41, Xu, Qian Q:
> Good catch, thx David
> Xueming, could you help check? Thx.
>
> From: David Marchand <david.marchand@redhat.com>
> >
> > Hello,
> >
> > Looking at a Intel CI report, even if the overall reported status is Success, we can
> > notice that a FC30-64 target has a FAIL status.
> >
> > Example:
> > http://mails.dpdk.org/archives/test-report/2020-January/112739.html
> >
> > | FC30-64 | FAIL | | | | |
> > | |
> >
> >
> > Thanks.
prev parent reply other threads:[~2020-01-10 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 10:15 David Marchand
2020-01-10 11:41 ` Xu, Qian Q
2020-01-10 13:07 ` Thomas Monjalon [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=2479331.KRxA6XjA2N@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.com \
--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).