DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>, ci@dpdk.org
Subject: Re: [dpdk-ci] Unit Testing on ARM Temporarily Disabled at UNH
Date: Fri, 8 Oct 2021 13:49:30 -0400	[thread overview]
Message-ID: <CAOeXdvb5PSx+O6nRa3P9TEGeWLe5SWanaP5LhfHhPLmfbnW46g@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ykTJQLQrBafE=iG=Z7rMS-M003ZkbDcJ11=kyQjXmp7w@mail.gmail.com>

On Fri, Oct 8, 2021 at 2:44 AM David Marchand <david.marchand@redhat.com> wrote:
> Hello Brandon,
> On Thu, Oct 7, 2021 at 6:18 PM Brandon Lo <blo@iol.unh.edu> wrote:
> > From the meeting minutes, I can see that you asked about the ARM unit
> > testing. ARM unit testing was disabled previously due to a conflict in
> > Jenkins which caused fluctuations when running the performance test.
> > Unfortunately, my investigations were interrupted by the Jenkins
> > update.
> >
> > Regardless, I have tracked down the issue and am currently working on
> > pushing up a fix. I suspect this fix should be up by Friday or early
> > next week.
> Ok, thank you.
> Keep me updated when it's enabled again, I want to monitor the
> func_reentrancy test on this platform.
> There was a recent change in this autotest.
> I don't expect this change to fix the issue we had before, but still
> worth checking.
> --
> David Marchand

Hi David,

I have pushed up the fix that should resolve the fluctuation conflict
within Jenkins. The unit test is now enabled again.
Please let me know if I should disable it again in case there are too
many failures.


Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824

      reply	other threads:[~2021-10-08 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 16:17 Brandon Lo
2021-10-08  6:44 ` David Marchand
2021-10-08 17:49   ` Brandon Lo [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOeXdvb5PSx+O6nRa3P9TEGeWLe5SWanaP5LhfHhPLmfbnW46g@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \


* 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).