Re: [dpdk-dev] Random failure in service_autotest

[Aaron Conole <aconole@redhat.com>]

David Marchand <david.marchand@redhat.com> writes:

> 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.
>
> 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 guess the service_lcore_attr_get failed, but with no useful
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.