[dpdk-dev] Random failure in service_autotest

[Lukasz Wojciechowski]

W dniu 15.07.2020 o 15:02, David Marchand pisze:
> On Wed, Jul 15, 2020 at 2:56 PM Aaron Conole <aconole at redhat.com> wrote:
>> I guess the service_lcore_attr_get failed, but with no useful
Why do you suspect service_lcore_attr_get() ?
>> information.  We should have the test suite app turn the log level all
>> the way up.  I realize it will increase the log data even higher, but
>> without it, we have no idea why this test failed.
>>
>> Something like the following
>> ---
>>
>> diff --git a/app/test/test.c b/app/test/test.c
>> index 94d26ab1f6..c47cb075f9 100644
>> --- a/app/test/test.c
>> +++ b/app/test/test.c
>> @@ -150,6 +150,9 @@ main(int argc, char **argv)
>>
>>          prgname = argv[0];
>>
>> +       rte_log_set_global_level(RTE_LOG_DEBUG);
>> +       rte_log_set_level(RTE_LOGTYPE_EAL, RTE_LOG_DEBUG);
>> +
>>          recursive_call = getenv(RECURSIVE_ENV_VAR);
>>          if (recursive_call != NULL) {
>>                  ret = do_recursive_call();
>> ---
>>
>> That way we can at least debug when it happens.
> Debugging is one thing.
> But here service_lcore_attr_get() has a lot of asserts that should
> trigger a straight error.
>
Yes, but without debugs enabled, the assert message won't be printed out.

-- 
Lukasz Wojciechowski
Principal Software Engineer

Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow at partner.samsung.com