From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] [dpdklab] What is the reliability of the community lab
Date: Fri, 16 Apr 2021 17:03:13 -0400 [thread overview]
Message-ID: <CAOeXdvbe3u37rZo2=hHub761T19QSCy=-WJ_fF+cTz-LrzG67Q@mail.gmail.com> (raw)
In-Reply-To: <11645160.apamBYaAj9@thomas>
We have completed our rolling migration to containers, so all of our
compilation jobs are running and catching up.
Our team has also worked on getting the DTS side of things back up and
running since the DTS issue had caused the pipelines to hang a bit.
Thanks,
Brandon
On Thu, Apr 15, 2021 at 2:33 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 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/
>
>
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
On Thu, Apr 15, 2021 at 2:33 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 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/
>
>
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
prev parent reply other threads:[~2021-04-16 21:03 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
2021-04-16 21:03 ` 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:
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='CAOeXdvbe3u37rZo2=hHub761T19QSCy=-WJ_fF+cTz-LrzG67Q@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=aconole@redhat.com \
--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).