I believe the physmem/numa error is just to throw us off -- a code bug but
an innocuous one at least for non NUMA systems; Damjan would know more.
Jon, I like your idea about it not quitting on the first error. And I guess
the "File Exists" error is also just something that happens after the
"real" error. Roughly speaking, but maybe Klement can give us a more
accurate statement about that.
Burt
On Mon, Mar 19, 2018 at 11:22 AM, Jon Loeliger <j...@netgate.com> wrote:
> On Fri, Mar 16, 2018 at 3:33 AM, Klement Sekera <ksek...@cisco.com> wrote:
>
>> This looks kinda like you have old papi installed somewhere.
>>
>> Please try `make test-wipe` and let me know how it goes.
>>
>> Thanks,
>> Klement
>
>
> These are clean build of top-of-tree. The 'make test-wipe' has no effect.
>
> I think the problem is that it doesn't quit at the first error, and tries
> to
> reopen one of the output files or directories a second time, not realizing
> it is already there.
>
>
>
> In one of the complaint directories, the stderr file contains this message:
>
> $ less /tmp/vpp-unittest-TestPAPIMessageParsing-P8q8OK/vpp_stderr.txt
>
> load_one_plugin:184: Loaded plugin: tlsmbedtls_plugin.so (mbedtls based
> TLS Engine)
> load_one_plugin:184: Loaded plugin: tlsopenssl_plugin.so (openssl based
> TLS Engine)
> work/vpp/build-root/install-vpp-native/vpp/bin/vpp[19872]:
> unix_physmem_region_alloc:172: physmem page for region 'buffers' allocated
> on the wrong numa node (requested 0 actual 4294967294)
>
> In the log.txt we find:
>
> 10:12:52,305 --- setUp() for TestPAPIMessageParsing.test_
> add_new_compound_type_with_array( New compound type with array ) called
> ---
> 10:12:52,305 Starting sleep for 0.1s (during setUp)
> 10:12:52,405 Finished sleep (during setUp) - slept 0.100102901459s (wanted
> 0.1s)
> 10:12:52,405 CLI: clear trace
> 10:12:53,132 --- addError() TestPAPIMessageParsing.test_
> add_new_compound_type_with_array( New compound type with array ) called,
> err is (<type 'exceptions.ValueError'>, ValueError(u'Duplicate message
> name: vl_api_ip4_fib_counter_t',), <traceback object at 0x62ea758>)
> 10:12:53,133 formatted exception is:
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
> testMethod()
> File "work/vpp/test/test_papi.py", line 281, in
> test_add_new_compound_type_with_array
> msglist.add_type(p[0], p[1:])
> File "build/bdist.linux-x86_64/egg/vpp_papi.py", line 590, in add_type
> typeonly=True)
> File "build/bdist.linux-x86_64/egg/vpp_papi.py", line 545, in
> add_message
> raise ValueError('Duplicate message name: ' + name)
> ValueError: Duplicate message name: vl_api_ip4_fib_counter_t
>
> 10:12:53,133 creating a link to the failed test
> 10:12:53,133 os.symlink(/tmp/vpp-unittest-TestPAPIMessageParsing-P8q8OK,
> /tmp/vpp-failed-unittests//vpp-unittest-TestPAPIMessageParsing-P8q8OK-
> FAILED)
> 10:12:53,133 --- tearDown() for TestPAPIMessageParsing.test_
> add_new_compound_type_with_array( New compound type with array ) called
> ---
> 10:12:53,134 CLI: show trace
>
> HTH,
> jdl
>
>
>
>
>
