Ed, these tests don't rely on keeping an interactive sesion up, like BFD tests
do. Fast box is required only to pass e.g. the BFD tests reliably enough.
These are only part of test-all and test-debug-all targets because the
jenkins infrastructure wasn't able to pass them reliably enough..
I'm sorry
Subject: Re: [vpp-dev] shadow build system change adding test-debug job
alright klement/dave
im a bit stuck again…
i get about an 60+% failure rate out of test-debug even with higher than normal
cpu settings (higher than just what i use for build verify)
always right here
19:43:38
alright klement/dave
im a bit stuck again…
i get about an 60+% failure rate out of test-debug even with higher than normal
cpu settings (higher than just what i use for build verify)
always right here
19:43:38
==
19
well sure enough…i doubled the cpu reservation and it all passed clean…
things are pretty quiet right now so ill throw it up again when things are busy
but right now I’m just happy to see a full test-all-debug pass.
thanks,
Ed
> On May 24, 2017, at 8:42 AM, Klement Sekera -X (ksekera - PANTHEO
I know that the functional BFD tests passed so unless there is a bug in
the tests, the failures are pretty much timing issues. From my
experience the load is the culprit as the BFD tests test interactive
sessions, which need to be kept alive. The timings currently are set at
300ms and for most test
right now its a VERY intentional mix…but depending on loading I could easily
see this coming up if those timings are strict.
To not dodge your question max loading on my slowest node would be 3 concurrent
builds on an Xeon™ E3-1240 v3 (4 cores @ 3.4Ghz)
yeah yeah stop laughing…..Do you have s
Hi Ed,
how fast are your boxes? And how many cores? The BFD tests struggle to meet
the aggresive timings on slower boxes...
Thanks,
Klement
Quoting Ed Kern (ejk) (2017-05-23 20:43:55)
>No problem.
>If anyone is curious in rubbernecking the accident that is the current
>test-all (at l
No problem.
If anyone is curious in rubbernecking the accident that is the current test-all
(at least for my build system)
adding a comment of
testall
SHOULD trigger and fire it off on my end.
make it all pass and you win a beer (or beverage of your choice)
Ed
On May 23, 2017, at 11:34 AM, Da
Ed,
Thanks for adding this to the shadow build system. Real data on the
cost and effectiveness of this will be most useful.
-daw-
On 5/23/2017 1:30 PM, Ed Kern (ejk) wrote:
In the vpp-dev call a couple hours ago there was a discussion of running
test-debug on a regular/default? basis.
As a
In the vpp-dev call a couple hours ago there was a discussion of running
test-debug on a regular/default? basis.
As a trial I’ve added a new job to the shadow build system:
vpp-test-debug-master-ubuntu1604
Will do a make test-debug, as part of verify set, as an ADDITIONAL job.
I gave a coupl
10 matches
Mail list logo
