From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: David Marchand <david.marchand@redhat.com>,
Van Haaren Harry <harry.van.haaren@intel.com>,
dpdklab <dpdklab@iol.unh.edu>
Cc: "Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Aaron Conole" <aconole@redhat.com>, dev <dev@dpdk.org>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: rte_service unit test failing randomly
Date: Wed, 5 Oct 2022 20:33:36 +0000 [thread overview]
Message-ID: <739ee0ca-ccbe-5918-c2af-18e77327a898@ericsson.com> (raw)
In-Reply-To: <CAJFAV8wcXZ_XhML=64HcV6Zs06PrB=UP9q5M6LWQhGvfLHmjEQ@mail.gmail.com>
On 2022-10-05 21:14, David Marchand wrote:
> Hello,
>
> The service_autotest unit test has been failing randomly.
> This is not something new.
> We have been fixing this unit test and the service code, here and there.
> For some time we were "fine": the failures were rare.
>
> But recenly (for the last two weeks at least), it started failing more
> frequently in UNH lab.
>
> The symptoms are linked to places where the unit test code is "waiting
> for some time":
>
> - service_lcore_attr_get:
> + TestCase [ 5] : service_lcore_attr_get failed
> EAL: Test assert service_lcore_attr_get line 422 failed: Service lcore
> not stopped after waiting.
>
>
> - service_may_be_active:
> + TestCase [15] : service_may_be_active failed
> ...
> EAL: Test assert service_may_be_active line 960 failed: Error: Service
> not stopped after 100ms
>
> Ideas?
>
>
> Thanks.
Do you run the test suite in a controlled environment? I.e., one where
you can trust that the lcore threads aren't interrupted for long periods
of time.
100 ms is not a long time if a SCHED_OTHER lcore thread competes for the
CPU with other threads.
next prev parent reply other threads:[~2022-10-05 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:14 David Marchand
2022-10-05 20:33 ` Mattias Rönnblom [this message]
2022-10-05 20:52 ` Thomas Monjalon
2022-10-05 21:33 ` Mattias Rönnblom
2022-10-06 6:53 ` Morten Brørup
2022-10-06 7:04 ` David Marchand
2022-10-06 7:50 ` Morten Brørup
2022-10-06 7:50 ` Mattias Rönnblom
2022-10-06 8:18 ` Morten Brørup
2022-10-06 8:59 ` Mattias Rönnblom
2022-10-06 9:49 ` Morten Brørup
2022-10-06 11:07 ` [dpdklab] " Lincoln Lavoie
2022-10-06 12:00 ` Morten Brørup
2022-10-06 17:52 ` Honnappa Nagarahalli
2022-10-06 13:51 ` Aaron Conole
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=739ee0ca-ccbe-5918-c2af-18e77327a898@ericsson.com \
--to=mattias.ronnblom@ericsson.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=harry.van.haaren@intel.com \
--cc=mb@smartsharesystems.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).