[dpdk-dev] Random failure in service_autotest

[Lukasz Wojciechowski]

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 at 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 at partner.samsung.com