automatic DPDK test reports
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: sys_stv@intel.com, test-report@dpdk.org,
	Qian Xu <qian.q.xu@intel.com>,
	Deepak Jain <deepak.k.jain@intel.com>
Cc: "Liu, Yu Y" <yu.y.liu@intel.com>
Subject: Re: [dpdk-test-report] |SUCCESS| pw37132 [PATCH v2 4/5] net/sfc/base: support FW subvariant choice
Date: Thu, 12 Apr 2018 19:37:23 +0100	[thread overview]
Message-ID: <1b158e12-9dd9-3623-99a9-2895dce618fc@intel.com> (raw)
In-Reply-To: <0590c7$1d6qi6@orsmga001.jf.intel.com>

On 4/12/2018 7:26 PM, sys_stv@intel.com wrote:
> Test-Label: Intel-compilation
> Test-Status: SUCCESS
> http://dpdk.org/patch/37132
> 
> _Compilation OK_
> 
> Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
> Date: Wed, 4 Apr 2018 15:17:07 +0100
> DPDK git baseline: Repo:dpdk, Branch:master, CommitID:34fbfa585cbfa5e3e1de5b0137e91ecfdc87e4f9
> 
> Patch37133-37132 --> compile pass
> Build Summary: 14 Builds Done, 14 Successful, 0 Failures


Hi Qian, Deepak,

There is a big delay in the build test report, which makes the output useless.

For example this is the build report, just received, for the patch sent on Wed,
4 Apr, 8 days ago. In the peak times like this 8 days latency is too much.

If the reason of the delay is backlog patches, I suggest clean the backlog and
do a clean start, it doesn't have much meaning to get build report of 8 days ago
doesn't have much meaning anyway.


Thanks,
ferruh

      reply	other threads:[~2018-04-12 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 18:26 sys_stv
2018-04-12 18:37 ` Ferruh Yigit [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=1b158e12-9dd9-3623-99a9-2895dce618fc@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=yu.y.liu@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).