From: David Marchand <david.marchand@redhat.com>
To: Van Haaren Harry <harry.van.haaren@intel.com>,
Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
Cc: Igor Romanov <igor.romanov@oktetlabs.ru>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Phil Yang <phil.yang@arm.com>, dev <dev@dpdk.org>,
Aaron Conole <aconole@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] Random failure in service_autotest
Date: Fri, 17 Jul 2020 17:19:02 +0200 [thread overview]
Message-ID: <CAJFAV8yh_k9iVUxrqPDvJeB4o4ZcZHuLktudhn2yhKaQ745NuQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wxabDLSmV7y6emAQ3-EwZiTvCQCRHKgc5BU2o9dx5wOQ@mail.gmail.com>
On Fri, Jul 17, 2020 at 10:56 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Wed, Jul 15, 2020 at 12:41 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> >
> > On 7/15/2020 11:14 AM, David Marchand wrote:
> > > Hello Harry and guys who touched the service code recently :-)
> > >
> > > I spotted a failure for the service UT in Travis:
> > > https://travis-ci.com/github/ovsrobot/dpdk/jobs/361097992#L18697
> > >
> > > I found only a single instance of this failure and tried to reproduce
> > > it with my usual "brute" active loop with no success so far.
> >
> > +1, I didn't able to reproduce it in my environment but observed it in the
> > Travis CI.
> >
> > >
> > > Any chance it could be due to recent changes?
> > > https://git.dpdk.org/dpdk/commit/?id=f3c256b621262e581d3edcca383df83875ab7ebe
> > > https://git.dpdk.org/dpdk/commit/?id=048db4b6dcccaee9277ce5b4fbb2fe684b212e22
>
> I can see more occurrences of the issue in the CI.
> I just applied the patch changing the log level for test assert, in
> the hope it will help.
And... we just got one with logs:
https://travis-ci.com/github/ovsrobot/dpdk/jobs/362109882#L18948
EAL: Test assert service_lcore_attr_get line 396 failed:
lcore_attr_get() didn't get correct loop count (zero)
It looks like a race between the service core still running and the
core resetting the loops attr.
--
David Marchand
next prev parent reply other threads:[~2020-07-17 15:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 10:14 David Marchand
2020-07-15 10:41 ` Ferruh Yigit
2020-07-17 8:56 ` David Marchand
2020-07-17 15:19 ` David Marchand [this message]
2020-07-17 20:31 ` Lukasz Wojciechowski
2020-07-17 22:38 ` Aaron Conole
2020-07-17 22:43 ` Honnappa Nagarahalli
2020-07-18 8:34 ` Phil Yang
2020-07-20 12:09 ` Van Haaren, Harry
2020-07-20 12:47 ` Lukasz Wojciechowski
2020-07-21 5:39 ` Honnappa Nagarahalli
2020-07-21 8:01 ` Van Haaren, Harry
2020-07-21 8:07 ` David Marchand
2020-07-21 8:16 ` Lukasz Wojciechowski
2020-07-21 15:09 ` Honnappa Nagarahalli
2020-07-21 15:38 ` Van Haaren, Harry
2020-07-21 16:21 ` Honnappa Nagarahalli
2020-07-15 12:56 ` Aaron Conole
2020-07-15 13:02 ` David Marchand
2020-07-15 13:09 ` Lukasz Wojciechowski
2020-07-15 13:28 ` David Marchand
2020-07-15 13:39 ` Aaron Conole
2020-07-15 20:26 ` Honnappa Nagarahalli
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=CAJFAV8yh_k9iVUxrqPDvJeB4o4ZcZHuLktudhn2yhKaQ745NuQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=igor.romanov@oktetlabs.ru \
--cc=l.wojciechow@partner.samsung.com \
--cc=phil.yang@arm.com \
/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).