HC Tests: mark BGP v6 tests as critical

TC13 of BGP tests was marked as EXPECTED_FAILING
due to HONEYCOMB-403,
but the error does not occur on 1807 nor master for some time.

Change-Id: I3d8f4ee78fed699927fed05e8fa070cfa95b2166
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

diff --git a/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot b/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
index b213abc..d418201 100644 (file)
--- a/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
+++ b/tests/honeycomb/func/mgmt-cfg-bgp-apihc-func.robot
@@ -258,8 +258,6 @@
 | | ... | [ver] Verify that the route is present in BGP
 | | ... | local RIB and VPP's routing table on each DUT.
 | | ...
 | | ... | [ver] Verify that the route is present in BGP
 | | ... | local RIB and VPP's routing table on each DUT.
 | | ...

-# HONEYCOMB-403: Missing writers for IPv6 BGP route
-| | [Tags] | EXPECTED_FAILING

 | | Given Peer operational data from Honeycomb should be
 | | ... | ${dut1_node} | ${dut2_to_dut1_ip}
 | | And Peer operational data from Honeycomb should be
 | | Given Peer operational data from Honeycomb should be
 | | ... | ${dut1_node} | ${dut2_to_dut1_ip}
 | | And Peer operational data from Honeycomb should be