automatic DPDK test reports
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
Cc: "dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	Test Report <test-report@dpdk.org>,
	 "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-test-report] [dpdklab] RE: |FAILURE| pw97549 [PATCH] [v2] eventdev: rx-adapter: improve enqueue buffer to circular buffer
Date: Tue, 31 Aug 2021 10:47:13 -0400	[thread overview]
Message-ID: <CAOeXdva5Gp8QaKvOpGyaG3ux2gMVH6MKYAjPBc3FeiW6Mhnukw@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB4882B22CAC5932520C965EFD87CC9@CO1PR11MB4882.namprd11.prod.outlook.com>

On Tue, Aug 31, 2021 at 8:23 AM Kundapura, Ganapati
<ganapati.kundapura@intel.com> wrote:
>
> Hi,
>    Any idea on why atomic_autotest is failing for this patch with only changes to commit header?
> In this malloc_autotest got passed without any changes in sources whereas it got failed for first patch - https://lab.dpdk.org/results/dashboard/patchsets/18384/
>
> Thanks,
> Ganapati

Hi Ganapati,

I will try to investigate the issue today.
For right now, I have disabled the unit test specifically on the arm
machine.

There were some efforts to try and figure out the reason behind the
intermittent failures, but I am not sure if there is any known root
cause at this moment.

Thanks,
Brandon




--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

  reply	other threads:[~2021-09-03  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  3:43 [dpdk-test-report] " dpdklab
2021-08-31 12:23 ` Kundapura, Ganapati
2021-08-31 14:47   ` Brandon Lo [this message]
2021-09-01 14:45     ` [dpdk-test-report] [dpdklab] " Kundapura, Ganapati

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=CAOeXdva5Gp8QaKvOpGyaG3ux2gMVH6MKYAjPBc3FeiW6Mhnukw@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=anatoly.burakov@intel.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=ganapati.kundapura@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=test-report@dpdk.org \
    /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).