Testing PullReq against Topology Tests

Build: #394 failed

Job: TopoTest Master arm7 failed

Job result summary

Completed
Duration
37 minutes
Flags
Custom revisionCustom build
Total tests
124

Tests

  • 124 tests in total
  • 8 tests failed
  • 8 failures are new
  • 15 tests were quarantined / skipped
  • 35 minutes taken in total.
New test failures 8
Status Test Duration
Collapse Failed test_bgp_l3vpn_to_bgp_direct test_adjacencies History
1 min
AssertionError: 3 tests failed
E   AssertionError: 3 tests failed
Collapse Failed test_bgp_rfapi_basic_sanity test_adjacencies History
1 min
AssertionError: 3 tests failed
E   AssertionError: 3 tests failed
Collapse Failed test_bgp_rfapi_basic_sanity_config2 test_adjacencies History
1 min
AssertionError: 3 tests failed
E   AssertionError: 3 tests failed
Collapse Failed test_ldp_topo1 test_linux_mpls_routes History
< 1 sec
AssertionError: Linux Kernel MPLS route output for router r2:   --- actual Linux Kernel MPLS route   +++ expected Linux Kernel MPLS route   @@ -1,3 +1,3 @@   +xx proto xx nexthopvia inet 10.0.2.3 dev r2-eth1 nexthopvia inet 10.0.3.3 dev r2-eth2    xx via inet 10.0.1.1 dev r2-eth0 proto xx    xx via inet 10.0.2.4 dev r2-eth1 proto xx   -xx via inet 10.0.3.3 dev r2-eth2 proto xx assert 1 == 0
E   AssertionError: Linux Kernel MPLS route output for router r2:
      --- actual Linux Kernel MPLS route
      +++ expected Linux Kernel MPLS route
      @@ -1,3 +1,3 @@
      +xx proto xx nexthopvia inet 10.0.2.3 dev r2-eth1 nexthopvia inet 10.0.3.3 dev r2-eth2
       xx via inet 10.0.1.1 dev r2-eth0 proto xx
       xx via inet 10.0.2.4 dev r2-eth1 proto xx
(2 more lines...)
Collapse Failed test_ldp_topo1 test_mpls_ldp_binding History
3 secs
AssertionError: MPLS LDP Interface binding output for router r4:   --- actual MPLS LDP binding output   +++ expected MPLS LDP binding output   @@ -12,4 +12,4 @@    ipv4 10.0.2.0/24          2.2.2.2         imp-null    imp-null          no    ipv4 10.0.2.0/24          3.3.3.3         imp-null    imp-null          no    ipv4 10.0.3.0/24          2.2.2.2         xxx         imp-null         yes   -ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null          no   +ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null         yes assert 1 == 0
E   AssertionError: MPLS LDP Interface binding output for router r4:
      --- actual MPLS LDP binding output
      +++ expected MPLS LDP binding output
      @@ -12,4 +12,4 @@
       ipv4 10.0.2.0/24          2.2.2.2         imp-null    imp-null          no
       ipv4 10.0.2.0/24          3.3.3.3         imp-null    imp-null          no
       ipv4 10.0.3.0/24          2.2.2.2         xxx         imp-null         yes
(3 more lines...)
Collapse Failed test_ldp_topo1 test_mpls_table History
2 secs
AssertionError: MPLS table output for router r2:   --- actual MPLS table output   +++ expected MPLS table output   @@ -2,5 +2,6 @@       Label     Type          Nexthop     Label    --------  -------  ---------------  --------          XX      LDP         10.0.1.1  implicit-null   +      XX      LDP         10.0.2.3  implicit-null          XX      LDP         10.0.2.4  implicit-null          XX      LDP         10.0.3.3  implicit-null assert 1 == 0
E   AssertionError: MPLS table output for router r2:
      --- actual MPLS table output
      +++ expected MPLS table output
      @@ -2,5 +2,6 @@
          Label     Type          Nexthop     Label
       --------  -------  ---------------  --------
             XX      LDP         10.0.1.1  implicit-null
(4 more lines...)
Collapse Failed test_ldp_topo1 test_zebra_ipv4_routingTable History
1 sec
AssertionError: IPv4 Zebra Routing Table verification failed for router r2:   --- actual IPv4 zebra routing table   +++ expected IPv4 zebra routing table   @@ -1,6 +1,6 @@    O>* 1.1.1.1/32 [110/10] via 10.0.1.1, r2-eth0, label implicit-null    O   2.2.2.2/32 [110/0] is directly connected, lo   -O>  3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1   +O>* 3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1, label implicit-null    O>* 4.4.4.4/32 [110/10] via 10.0.2.4, r2-eth1, label implicit-null    O   10.0.1.0/24 [110/10] is directly connected, r2-eth0    O   10.0.2.0/24 [110/10] is directly connected, r2-eth1 assert 1 == 0
E   AssertionError: IPv4 Zebra Routing Table verification failed for router r2:
      --- actual IPv4 zebra routing table
      +++ expected IPv4 zebra routing table
      @@ -1,6 +1,6 @@
       O>* 1.1.1.1/32 [110/10] via 10.0.1.1, r2-eth0, label implicit-null
       O   2.2.2.2/32 [110/0] is directly connected, lo
      -O>  3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1
(5 more lines...)
Collapse Failed test_ldp_vpls_topo1 test_rib History
3 mins
AssertionError: "r1" JSON output mismatches the expected result assert json value is different (   --- Expected value   +++ Current value   @@ -3,0 +4,2 @@   +        "internalFlags": 16,    +        "internalStatus": 2,    @@ -9 +11 @@   -                "fib": true,    +                "flags": 1,    @@ -17 +19 @@   -                "fib": true,    +                "flags": 1,    @@ -25 +27,2 @@   -        "selected": true   +        "selected": true,    +        "uptime": "00:04:02")
E   AssertionError: "r1" JSON output mismatches the expected result
    assert json value is different (
      --- Expected value
      +++ Current value
      @@ -3,0 +4,2 @@
      +        "internalFlags": 16, 
      +        "internalStatus": 2, 
(10 more lines...)

Error summary

The build generated some errors. See the full build log for more details.

@@ -12,4 +12,4 @@
ipv4 10.0.2.0/24          2.2.2.2         imp-null    imp-null          no
ipv4 10.0.2.0/24          3.3.3.3         imp-null    imp-null          no
ipv4 10.0.3.0/24          2.2.2.2         xxx         imp-null         yes
-ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null          no
+ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null         yes
2018-11-27 22:21:55,650 ERROR: assert failed at "test_ldp_topo1/test_mpls_ldp_binding": MPLS LDP Interface binding output for router r4:
  --- actual MPLS LDP binding output
  +++ expected MPLS LDP binding output
  @@ -12,4 +12,4 @@
   ipv4 10.0.2.0/24          2.2.2.2         imp-null    imp-null          no
   ipv4 10.0.2.0/24          3.3.3.3         imp-null    imp-null          no
   ipv4 10.0.3.0/24          2.2.2.2         xxx         imp-null         yes
  -ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null          no
  +ipv4 10.0.3.0/24          3.3.3.3         xxx         imp-null         yes
assert 1 == 0
r2 failed IPv4 Zebra Routing Table Check:
--- actual IPv4 zebra routing table
+++ expected IPv4 zebra routing table
@@ -1,6 +1,6 @@
O>* 1.1.1.1/32 [110/10] via 10.0.1.1, r2-eth0, label implicit-null
O   2.2.2.2/32 [110/0] is directly connected, lo
-O>  3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1
+O>* 3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1, label implicit-null
O>* 4.4.4.4/32 [110/10] via 10.0.2.4, r2-eth1, label implicit-null
O   10.0.1.0/24 [110/10] is directly connected, r2-eth0
O   10.0.2.0/24 [110/10] is directly connected, r2-eth1
2018-11-27 22:21:57,507 ERROR: assert failed at "test_ldp_topo1/test_zebra_ipv4_routingTable": IPv4 Zebra Routing Table verification failed for router r2:
  --- actual IPv4 zebra routing table
  +++ expected IPv4 zebra routing table
  @@ -1,6 +1,6 @@
   O>* 1.1.1.1/32 [110/10] via 10.0.1.1, r2-eth0, label implicit-null
   O   2.2.2.2/32 [110/0] is directly connected, lo
  -O>  3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1
  +O>* 3.3.3.3/32 [110/10] via 10.0.2.3, r2-eth1, label implicit-null
   O>* 4.4.4.4/32 [110/10] via 10.0.2.4, r2-eth1, label implicit-null
   O   10.0.1.0/24 [110/10] is directly connected, r2-eth0
   O   10.0.2.0/24 [110/10] is directly connected, r2-eth1
assert 1 == 0
r2 failed MPLS table output Check:
--- actual MPLS table output
+++ expected MPLS table output
@@ -2,5 +2,6 @@
    Label     Type          Nexthop     Label
--------  -------  ---------------  --------
       XX      LDP         10.0.1.1  implicit-null
+      XX      LDP         10.0.2.3  implicit-null
       XX      LDP         10.0.2.4  implicit-null
       XX      LDP         10.0.3.3  implicit-null
2018-11-27 22:22:00,196 ERROR: assert failed at "test_ldp_topo1/test_mpls_table": MPLS table output for router r2:
  --- actual MPLS table output
  +++ expected MPLS table output
  @@ -2,5 +2,6 @@
      Label     Type          Nexthop     Label
   --------  -------  ---------------  --------
         XX      LDP         10.0.1.1  implicit-null
  +      XX      LDP         10.0.2.3  implicit-null
         XX      LDP         10.0.2.4  implicit-null
         XX      LDP         10.0.3.3  implicit-null
assert 1 == 0
r2 failed Linux Kernel MPLS route output Check:
--- actual Linux Kernel MPLS route
+++ expected Linux Kernel MPLS route
@@ -1,3 +1,3 @@
+xx proto xx nexthopvia inet 10.0.2.3 dev r2-eth1 nexthopvia inet 10.0.3.3 dev r2-eth2
xx via inet 10.0.1.1 dev r2-eth0 proto xx
xx via inet 10.0.2.4 dev r2-eth1 proto xx
-xx via inet 10.0.3.3 dev r2-eth2 proto xx
2018-11-27 22:22:00,401 ERROR: assert failed at "test_ldp_topo1/test_linux_mpls_routes": Linux Kernel MPLS route output for router r2:
  --- actual Linux Kernel MPLS route
  +++ expected Linux Kernel MPLS route
  @@ -1,3 +1,3 @@
  +xx proto xx nexthopvia inet 10.0.2.3 dev r2-eth1 nexthopvia inet 10.0.3.3 dev r2-eth2
   xx via inet 10.0.1.1 dev r2-eth0 proto xx
   xx via inet 10.0.2.4 dev r2-eth1 proto xx
  -xx via inet 10.0.3.3 dev r2-eth2 proto xx
assert 1 == 0
2018-11-27 22:27:24,828 ERROR: 'router_json_cmp' failed after 220.49 seconds
2018-11-27 22:27:24,834 ERROR: assert failed at "test_ldp_vpls_topo1/test_rib": "r1" JSON output mismatches the expected result
assert json value is different (
  --- Expected value
  +++ Current value
  @@ -3,0 +4,2 @@
  +        "internalFlags": 16,
  +        "internalStatus": 2,
  @@ -9 +11 @@
  -                "fib": true,
  +                "flags": 1,
  @@ -17 +19 @@
  -                "fib": true,
  +                "flags": 1,
  @@ -25 +27,2 @@
  -        "selected": true
  +        "selected": true,
  +        "uptime": "00:04:02")
*** defaultIntf: warning: lm has no interfaces
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument