DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Aaron Conole <aconole@redhat.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	sys_stv@intel.com, test-report@dpdk.org,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-test-report] |FAILURE| pw(93150) [v2] app/testpmd: add CLI for action meter color
Date: Tue, 11 May 2021 17:33:00 +0200	[thread overview]
Message-ID: <1795147.WKu47Booy6@thomas> (raw)
In-Reply-To: <f7twns55o7p.fsf@redhat.com>

11/05/2021 16:39, Aaron Conole:
> Ferruh Yigit <ferruh.yigit@intel.com> writes:
> 
> > On 5/11/2021 10:51 AM, sys_stv@intel.com wrote:
> >> 
> >> Test-Label: Intel-compilation
> >> Test-Status: FAILURE
> >> http://dpdk.org/patch/93150
> >> 
> >> _Compilation issues_
> >> 
> >> Submitter: Haifei Luo <haifeil@nvidia.com>
> >> Date: 2021-05-11 09:28:10
> >> Reply_mail: 20210511092810.22801-1-haifeil@nvidia.com
> >> 
> >> DPDK git baseline: Repo:dpdk-next-net, CommitID: 8b1e6d9eb25cbd86a0ad9b990eaf598dc9f5a15a
> >> 
> >
> > Hi Zhaoyan,
> >
> > Thomas reported that the baseline that patch is merged on is a very old commit,
> > that is from mid April. It looks like something went wrong on updating the tree.
> > And this is causing the build error.
> >
> > Can you please check why the tree is not updated properly?
> 
> Perhaps folks aren't updating the next- trees often enough.

It should be updated before each test.




  reply	other threads:[~2021-05-11 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d0e636$ijmd2r@fmsmga005-auth.fm.intel.com>
2021-05-11 11:43 ` Ferruh Yigit
2021-05-11 14:39   ` Aaron Conole
2021-05-11 15:33     ` Thomas Monjalon [this message]
2021-05-12 13:03       ` Aaron Conole

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=1795147.WKu47Booy6@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --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).