Mark TCP dataplane test as notready until bandwith profile enforcement issue fixed
Change-Id: I6625c90fe35c9139aed2589438bdfdda42b9d99a
diff --git a/tests/dt-workflow/Voltha_DT_PODTests.robot b/tests/dt-workflow/Voltha_DT_PODTests.robot
index 4a90cc2..50debd8 100644
--- a/tests/dt-workflow/Voltha_DT_PODTests.robot
+++ b/tests/dt-workflow/Voltha_DT_PODTests.robot
@@ -365,7 +365,7 @@
Data plane verification using TCP for DT
[Documentation] Test bandwidth profile is met and not exceeded for each subscriber.
... Assumes iperf3 and jq installed on client and iperf -s running on DHCP server
- [Tags] dataplaneDt BandwidthProfileTCPDt VOL-3061
+ [Tags] dataplaneDt BandwidthProfileTCPDt VOL-3061 notready
[Setup] Start Logging BandwidthProfileTCPDt
[Teardown] Run Keywords Collect Logs
... AND Stop Logging BandwidthProfileTCPDt
diff --git a/tests/functional/Voltha_PODTests.robot b/tests/functional/Voltha_PODTests.robot
index 4e9c122..55d176d 100644
--- a/tests/functional/Voltha_PODTests.robot
+++ b/tests/functional/Voltha_PODTests.robot
@@ -454,7 +454,7 @@
Data plane verification using TCP
[Documentation] Test bandwidth profile is met and not exceeded for each subscriber.
... Assumes iperf3 and jq installed on client and iperf -s running on DHCP server
- [Tags] dataplane BandwidthProfileTCP VOL-2052
+ [Tags] dataplane BandwidthProfileTCP VOL-2052 notready
[Setup] Start Logging BandwidthProfileTCP
[Teardown] Run Keywords Collect Logs
... AND Stop Logging BandwidthProfileTCP