o"
Subject: Re: [vpp-dev] Spurious make test failure (container POC)
these are NOT with verify…
specifically with test-debug that I added as a separate run at someones
request..(sorry can’t remember who at this moment)
Ed
On Aug 10, 2017, at 1:07 AM, Klement Sekera -X (ksekera - P
these are NOT with verify…
specifically with test-debug that I added as a separate run at someones
request..(sorry can’t remember who at this moment)
Ed
On Aug 10, 2017, at 1:07 AM, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES
at Cisco) mailto:ksek...@cisco.com>> wrote:
The 2 minute ti
The 2 minute timeout is the result of my recent change. The framework
now forks and runs the test in a child process, and if the child process
fails to send a keep-alive (sent when a test case starts), then it's
killed. Otherwise there'd be no way to recover from stuck mutex or
deadlock..
Are you
klement,
ok…ill think about how to do that without too much trouble in its current
state..
in the meantime…blowing out the cpu and memory a bit changed the error……
21:49:42 create 1k of p2p subifs
OK
21:49:42
=
Ed,
it'd help if you could collect log.txt from a failed run so we could
peek under the hood... please see my other email in this thread...
Thanks,
Klement
Quoting Ed Kern (ejk) (2017-08-09 20:48:46)
>this is not you…or this patch…
>the make test-debug has had a 90+% failure rate (read n
Hi Dave,
this looks like something got stuck - and the only thing I know
which can get the framework stuck like this is if vpp coredumps mid-API,
in which case, python gets stuck doing unix_shared_memory_queue_sub(). I
actually pushed a patch today, which makes the test framework to fork at
start
this is not you…or this patch…
the make test-debug has had a 90+% failure rate (read not 100%) for at least
the last 100 builds
(far back as my current logs go but will probably blow that out a bit now)
you hit the one that is seen most often… on that create 1k of p2p subifs
the other much less
Please see https://gerrit.fd.io/r/#/c/7927, and
http://jenkins.ejkern.net:8080/job/vpp-test-debug-master-ubuntu1604/1056/con
sole
The patch in question is highly unlikely to cause this failure...
14:37:11
