From: Thomas Monjalon <thomas@monjalon.net>
To: Brandon Lo <blo@iol.unh.edu>
Cc: dpdklab <dpdklab@iol.unh.edu>, ci@dpdk.org, aconole@redhat.com
Subject: Re: [dpdk-ci] [dpdklab] What is the reliability of the community lab
Date: Thu, 15 Apr 2021 20:33:53 +0200 [thread overview]
Message-ID: <11645160.apamBYaAj9@thomas> (raw)
In-Reply-To: <CAOeXdvZuVo5Sty6mWfca_tQcasFvDpVVo7h45yp7H8tKA4KQCw@mail.gmail.com>
15/04/2021 20:26, Brandon Lo:
> 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.
You should avoid running tests when the platform is not ready.
It was giving false positives.
> 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.
The lab seems stopped currently.
There are issues for a week now.
What are the news today?
> 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/
next prev parent reply other threads:[~2021-04-15 18:33 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 ` [dpdk-ci] [dpdklab] " Brandon Lo
2021-04-15 18:33 ` Thomas Monjalon [this message]
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=11645160.apamBYaAj9@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/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).