Klement,
I just pulled the top-of-tree on master and ran only VCL tests on my
18.04 box and they all passed (see below). Another strange thing about
your failure is that the test that failed is NOT an extended test.
I'm currently working on a patch (https://gerrit.fd.io/r/#/c/13215/) to
shorten the run time for the extended tests and convert them to regular
tests. In the past, I have seen some unexplained failures of some of
the extended tests. I'll let you know if I encounter any of them again.
Thanks,
-daw-
----- %< -----
TEST=vcl.* make test-ext
. . .
make[2]: Leaving directory '/scratch/dwallacelf/lf/vpp/test/ext'
==============================================================================
Sanity test case - verify if VPP is able to start
==============================================================================
Running tests using custom test runner
Active filters: file=test_vcl.py, class=None, function=None
Adding tests from directory tree /scratch/dwallacelf/lf/vpp/test
28 out of 858 tests match specified filters
==============================================================================
VCL Thru Host Stack Tests
==============================================================================
run LDP thru host stack echo test OK
run VCL thru host stack echo test OK
==============================================================================
VCL Thru Host Stack Extended B Tests
==============================================================================
run LDP thru host stack bi-directional (multiple sockets) test OK
==============================================================================
VCL Thru Host Stack Iperf Tests
==============================================================================
run LDP thru host stack iperf3 test OK
==============================================================================
VCL Thru Host Stack Extended D Tests
==============================================================================
run VCL thru host stack uni-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Thru Host Stack Tests
==============================================================================
run LDP IPv6 thru host stack echo test OK
run VCL IPv6 thru host stack echo test OK
==============================================================================
VCL Cut Thru Tests
==============================================================================
run LDP cut thru bi-directional (multiple sockets) test OK
run LDP cut thru echo test OK
run LDP cut thru iperf3 test OK
run LDP cut thru uni-directional (multiple sockets) test OK
run VCL cut thru bi-directional (multiple sockets) test OK
run VCL cut thru echo test OK
run VCL cut thru uni-directional (multiple sockets) test OK
==============================================================================
VCL Thru Host Stack Extended C Tests
==============================================================================
run LDP thru host stack uni-directional (multiple sockets) test OK
==============================================================================
VCL Thru Host Stack NSession Bidir Tests
==============================================================================
run VCL thru host stack bi-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Thru Host Stack Extended A Tests
==============================================================================
run VCL thru host stack bi-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Cut Thru Tests
==============================================================================
run LDP IPv6 cut thru bi-directional (multiple sockets) test OK
run LDP IPv6 cut thru echo test OK
run LDP IPv6 cut thru iperf3 test OK
run LDP IPv6 cut thru uni-directional (multiple sockets) test OK
run VCL IPv6 cut thru bi-directional (multiple sockets) test OK
run VCL IPv6 cut thru echo test OK
run VCL IPv6 cut thru uni-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Thru Host Stack Extended C Tests
==============================================================================
run LDP thru host stack uni-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Thru Host Stack Extended B Tests
==============================================================================
run LDP thru host stack bi-directional (multiple sockets) test OK
==============================================================================
VCL IPv6 Thru Host Stack Iperf Tests
==============================================================================
run LDP thru host stack iperf3 test OK
==============================================================================
VCL IPv6 Thru Host Stack Extended D Tests
==============================================================================
run VCL thru host stack uni-directional (multiple sockets) test OK
Ran 28 tests in 250.800s
OK
==============================================================================
TEST RESULTS:
Scheduled tests: 28
Executed tests: 28
Passed tests: 28
==============================================================================
Test run was successful
----- %< -----
On 11/15/2018 5:47 AM, Klement Sekera via Lists.Fd.Io wrote:
Hi all,
I'm seeing failures on master branch on ubuntu 18.04 when invoking `make
test-ext`
FAILURES AND ERRORS IN TESTS:
Testcase name: VCL Cut Thru Tests
FAILURE: run VCL cut thru uni-directional (multiple sockets) test
Testcase name: L2BD Test Case
ERROR: L2BD MAC learning dual-loop test
ERROR: L2BD MAC learning dual-loop test
ERROR: L2BD MAC learning single-loop test
Testcase name: Classifier PBR Test Case
ERROR: IP PBR test
digging a bit further, L2BD failure also occurs in `make test-debug`,
while it doesn't appear in `make test`. This is a core due to assert.
I think we should run both `make test` (release build) and `make
test-debug` (debug build) as part of verify process. If it was up to me,
I would run all the tests which we have in the verify job.
Thoughts?
Regards,
Klement
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11257): https://lists.fd.io/g/vpp-dev/message/11257
Mute This Topic: https://lists.fd.io/mt/28144643/675079
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11269): https://lists.fd.io/g/vpp-dev/message/11269
Mute This Topic: https://lists.fd.io/mt/28144643/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
