From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
To: David Marchand <david.marchand@redhat.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Phil Yang <Phil.Yang@arm.com>, Aaron Conole <aconole@redhat.com>,
Igor Romanov <igor.romanov@oktetlabs.ru>, dev <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] Random failure in service_autotest
Date: Tue, 21 Jul 2020 10:16:22 +0200 [thread overview]
Message-ID: <893ded39-89b6-f693-56eb-1f60fbdb8b42@partner.samsung.com> (raw)
In-Reply-To: <CAJFAV8zHT5-hjTyCCs=t2zt+upsLE5TnW-=YgfQv07qe9SCRQQ@mail.gmail.com>
W dniu 21.07.2020 o 10:07, David Marchand pisze:
> On Tue, Jul 21, 2020 at 10:01 AM Van Haaren, Harry
> <harry.van.haaren@intel.com> wrote:
>>>>> Honnappa's suggestion in the other reply seems to not work here, as the
>>>> "service_may_be_active"
>>>>> won't get updated if the service core is stopped after running its final
>>>> iteration..?
>>> This also is a problem.
>>> This needs to be fixed by setting 'service_active_on_lcore' immediately after the
>>> service completes running in 'service_run' (rather than waiting for the next
>>> iteration of service_run).
>> This is a different bug - not directly related to the service_autotest issue reported
>> here. I'll keep focus & resolve that issue first as it has higher priorty due to CI failures.
> Is the current bug caught by the CI something introduced by the recent changes?
No, I believe it's not. It's a lack of synchronization issue in test
between test procedure and service core that happens to show very
rarely. That's why it was so hard to reproduce.
>
--
Lukasz Wojciechowski
Principal Software Engineer
Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow@partner.samsung.com
next prev parent reply other threads:[~2020-07-21 8:16 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
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 [this message]
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=893ded39-89b6-f693-56eb-1f60fbdb8b42@partner.samsung.com \
--to=l.wojciechow@partner.samsung.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=igor.romanov@oktetlabs.ru \
--cc=nd@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).