diff options
| author |   Peter Mikus <pmikus@cisco.com> | 2018-05-07 13:38:29 +0200 |
|---|---|---|
| committer | Peter Mikus <pmikus@cisco.com> | 2018-05-07 13:42:14 +0200 |
| commit | f65135a3dd0602e7657237ca438ee1c0389d3f04 (patch) | |
| tree | 00ab16593ad850c06a75099bb0b63c9811080162 | |
| parent | d09989f2b4bf6adb49e3b8cecbb5f5f00c9abd19 (diff) | |
FIX: Small inconsistencies in report sections
Change-Id: I0c27300678414bd3baecccd8e51ca0dc15af73d5
Signed-off-by: Peter Mikus <pmikus@cisco.com>
5 files changed, 11 insertions, 13 deletions
diff --git a/docs/report/csit_framework_documentation/csit_test_naming.rst b/docs/report/csit_framework_documentation/csit_test_naming.rst index 6c24dc1ad5..253d6992f7 100644 --- 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 02651d7e53..56d0e1e8fd 100644 --- 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 fda35072ef..1cd5def87d 100644 --- 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
-----------------------
-CSIT |release| follows a common structured naming convention for all
-performance and system functional tests, introduced in CSIT |release-1|.
+CSIT |release| follows a common structured naming convention for all 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
-`CSIT test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
+The naming should be intuitive for majority of the tests. Complete description
+of CSIT test naming convention is provided on :ref:`csit_test_naming`..
Here few illustrative examples of the new naming usage for functional test
suites:
diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst index fb5737c4fc..7677b5546a 100644 --- 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 |
| | regression. | | -3%..-7%. Affects IPSec SW tests, QAT HW tests not affected. |
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+
-| 5 | High failure rate of creating working container | CSIT-1065 | Orchestrated container topology tests failing data plane |
-| | topologies with K8s/Ligato orchestration. | | verification indicating configuration issue. Suspected issue |
-| | | | with Ligato vpp-agent. |
+| 5 | High failure rate of creating working container | CSIT-1065 | About 20% of orchestrated container topology tests failing data |
+| | topologies with K8s/Ligato orchestration. | | plane verification indicating configuration issue. Suspected |
+| | | | issue with Ligato vpp-agent. |
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+
diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst index c9bc0c2a35..6682226651 100644 --- 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`. |