From: Thomas Monjalon <thomas@monjalon.net>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
ci@dpdk.org, sys_stv <sys_stv@intel.com>
Subject: Re: [dpdk-ci] Failure in Intel CI
Date: Wed, 11 Mar 2020 09:20:14 +0100 [thread overview]
Message-ID: <3892782.1IzOArtZ34@xps> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA41EFB97D@SHSMSX104.ccr.corp.intel.com>
11/03/2020 03:07, Chen, Zhaoyan:
> Hi, David,
>
> The applying failure is caused by our CI is download patches from patchwork. (it's a little slow and unstable in PRC)
>
> We are working on separating "CI exception" and "real failure". But 1 question, for patchwork report,
> do you think what kind of result status for any exception in CI workflow?
If you cannot run the test, you should not report it at all.
prev parent reply other threads:[~2020-03-11 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 9:42 David Marchand
2020-03-11 2:07 ` Chen, Zhaoyan
2020-03-11 8:20 ` 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=3892782.1IzOArtZ34@xps \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.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).