DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdklab <dpdklab@iol.unh.edu>, ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdklab] What is the reliability of the community lab
Date: Thu, 15 Apr 2021 14:26:03 -0400	[thread overview]
Message-ID: <CAOeXdvZuVo5Sty6mWfca_tQcasFvDpVVo7h45yp7H8tKA4KQCw@mail.gmail.com> (raw)
In-Reply-To: <2891195.MathiC2lse@thomas>

Hi Thomas,

For the ABI check failure, we were working on a few migration-related
changes that caused this issue. We have fixed the underlying cause and
the rolling migration will be completed soon. The test will be rerun
and reported back up to patchworks as well.
We are also in the process of adding more monitoring for failure
results that are not limited to only infrastructure failures, i.e.
failures caused by a test's return value will alert us in a separate
category which will allow us to validate the result.

Thanks,
Brandon

On Wed, Apr 14, 2021 at 8:10 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> We still have some severe reliability issues with the community lab.
> One under investigation, waiting for a bisect, is making the lab crashing.
>
> Another one I would like to understand is about the ABI check.
> Why the test is failing (which is normal) in Travis and GitHub
> but passing in the community lab?
>
> See this example:
> https://patches.dpdk.org/project/dpdk/patch/1618283653-16510-6-git-send-email-xuemingl@nvidia.com/
>
>


--

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-04-15 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 12:10 [dpdk-ci] " Thomas Monjalon
2021-04-15 18:26 ` Brandon Lo [this message]
2021-04-15 18:33   ` [dpdk-ci] [dpdklab] " Thomas Monjalon
2021-04-16 21:03     ` Brandon Lo

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=CAOeXdvZuVo5Sty6mWfca_tQcasFvDpVVo7h45yp7H8tKA4KQCw@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).