FIX: Small inconsistencies in report sections

Change-Id: I0c27300678414bd3baecccd8e51ca0dc15af73d5
Signed-off-by: Peter Mikus <pmikus@cisco.com>

diff --git a/docs/report/csit_framework_documentation/csit_test_naming.rst b/docs/report/csit_framework_documentation/csit_test_naming.rst
index 6c24dc1..253d699 100644 (file)
--- a/docs/report/csit_framework_documentation/csit_test_naming.rst
+++ b/docs/report/csit_framework_documentation/csit_test_naming.rst
@@ -7,7 +7,7 @@ Background
 ----------
 
 CSIT |release| follows a common structured naming convention for all
-performance and system functional tests, introduced in CSIT |release-1|.
+performance and system functional tests, introduced in CSIT rls1701.
 
 The naming should be intuitive for majority of the tests. Complete
 description of CSIT test naming convention is provided on

diff --git a/docs/report/dpdk_performance_tests/overview.rst b/docs/report/dpdk_performance_tests/overview.rst
index 02651d7..56d0e1e 100644 (file)
--- a/docs/report/dpdk_performance_tests/overview.rst
+++ b/docs/report/dpdk_performance_tests/overview.rst
@@ -116,11 +116,10 @@ Performance Tests Naming
 ------------------------
 
 CSIT |release| follows a common structured naming convention for all performance
-and system functional tests, introduced in CSIT |release-1|.
+and system functional tests, introduced in CSIT rls1701.
 
 The naming should be intuitive for majority of the tests. Complete description
-of CSIT test naming convention is provided on `CSIT test naming wiki
-<https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
+of CSIT test naming convention is provided on :ref:`csit_test_naming`.
 
 Methodology: Multi-Core and Multi-Threading
 -------------------------------------------

diff --git a/docs/report/vpp_functional_tests/overview.rst b/docs/report/vpp_functional_tests/overview.rst
index fda3507..1cd5def 100644 (file)
--- a/docs/report/vpp_functional_tests/overview.rst
+++ b/docs/report/vpp_functional_tests/overview.rst
@@ -127,12 +127,11 @@ results listed in this report:
 Functional Tests Naming\r
 -----------------------\r
 \r
-CSIT |release| follows a common structured naming convention for all\r
-performance and system functional tests, introduced in CSIT |release-1|.\r
+CSIT |release| follows a common structured naming convention for all performance\r
+and system functional tests, introduced in CSIT rls1701.\r
 \r
-The naming should be intuitive for majority of the tests. Complete\r
-description of CSIT test naming convention is provided on\r
-`CSIT test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
+The naming should be intuitive for majority of the tests. Complete description\r
+of CSIT test naming convention is provided on :ref:`csit_test_naming`..\r
 \r
 Here few illustrative examples of the new naming usage for functional test\r
 suites:\r

diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst
index fb5737c..7677b55 100644 (file)
--- a/docs/report/vpp_performance_tests/csit_release_notes.rst
+++ b/docs/report/vpp_performance_tests/csit_release_notes.rst
@@ -125,7 +125,7 @@ List of known issues in CSIT |release| for VPP performance tests:
 | 4 | IPSec (software, no QAT HW) throughput          | CSIT-1064  | IPSec throughput regression: NDR -3%..-8%, PDR -2%..-8%, MRR    |\r
 |   | regression.                                     |            | -3%..-7%. Affects IPSec SW tests, QAT HW tests not affected.    |\r
 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r
-| 5 | High failure rate of creating working container | CSIT-1065  | Orchestrated container topology tests failing data plane        |\r
-|   | topologies with K8s/Ligato orchestration.       |            | verification indicating configuration issue. Suspected issue    |\r
-|   |                                                 |            | with Ligato vpp-agent.                                          |\r
+| 5 | High failure rate of creating working container | CSIT-1065  | About 20% of orchestrated container topology tests failing data |\r
+|   | topologies with K8s/Ligato orchestration.       |            | plane verification indicating configuration issue. Suspected    |\r
+|   |                                                 |            | issue with Ligato vpp-agent.                                    |\r
 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r

diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst
index 3dbabd6..d9e271e 100644 (file)
--- a/docs/report/vpp_performance_tests/overview.rst
+++ b/docs/report/vpp_performance_tests/overview.rst
@@ -232,7 +232,7 @@ Performance Tests Naming
 ------------------------
 
 CSIT |release| follows a common structured naming convention for all performance
-and system functional tests, introduced in CSIT |release-1|.
+and system functional tests, introduced in CSIT rls1701.
 
 The naming should be intuitive for majority of the tests. Complete description
 of CSIT test naming convention is provided on :ref:`csit_test_naming`.