diff mbox series

web: updated ci testing information

Message ID 20221215141421.10065-1-lylavoie@iol.unh.edu (mailing list archive)
State New
Headers show
Series web: updated ci testing information | expand

Commit Message

Lincoln Lavoie Dec. 15, 2022, 2:14 p.m. UTC 
* Add link to the community lab testing coverage.
* Added LTS staging branches to input list.
* Updated VSPERF to ViNePerf to align with its real name.

Signed-off-by: Lincoln Lavoie <lylavoie@iol.unh.edu>
---
 content/testing/_index.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

Comments

Thomas Monjalon Jan. 13, 2023, 2:05 p.m. UTC | #1 
15/12/2022 15:14, Lincoln Lavoie:
> @@ -42,6 +45,8 @@ There are three kinds of inputs to be tested:
>  with [patchwork](//patches.dpdk.org/project/dpdk/list/)
>  - per-commit testing after merges
>  in mainline or dpdk-next- [repositories](//git.dpdk.org/)
> +- per-commit testing of LTS staging commits in the
> +*-staging branches of the [stable repository](//git.dpdk.org/dpdk-stable/)

Instead of adding 4th type (note "there are three kinds of inputs" above),
may I suggest to reword the previous type to include stable repository?

 - per-commit testing after merges
-in mainline or dpdk-next- [repositories](//git.dpdk.org/)
+in mainline, stable or dpdk-next-* [repositories](//git.dpdk.org/)

I think the name of the branch is a detail here.

If you agree I can push with this change.
diff mbox series

Patch

diff --git a/content/testing/_index.md b/content/testing/_index.md
index db9e032..d5a9f1b 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -14,7 +14,10 @@  There are various ways of contributing to the CI effort:
 
 One specific lab instance,
 named [community lab](//lab.dpdk.org/results/dashboard/about),
-is hosted at [UNH-IOL](//www.iol.unh.edu).
+is hosted at [UNH-IOL](//www.iol.unh.edu).  
+A view of the
+current [test coverage](//dpdkdashboard.iol.unh.edu/results/dashboard/test-matrix/)
+of the lab is automatically generated based on recent test runs.
 
 
 ## CI Testing Goals
@@ -42,6 +45,8 @@  There are three kinds of inputs to be tested:
 with [patchwork](//patches.dpdk.org/project/dpdk/list/)
 - per-commit testing after merges
 in mainline or dpdk-next- [repositories](//git.dpdk.org/)
+- per-commit testing of LTS staging commits in the
+*-staging branches of the [stable repository](//git.dpdk.org/dpdk-stable/)
 - per-release testing
 including [release candidates](//git.dpdk.org/dpdk/refs/)
 of all [branches](//git.dpdk.org/dpdk-stable/refs/)
@@ -143,6 +148,6 @@  The testing infrastructure work is coordinated in three complementary forums:
 - [DPDK devtools](//git.dpdk.org/dpdk/tree/devtools/)
 - [DPDK apps](//git.dpdk.org/dpdk/tree/app/)
 - [DPDK Test Suite (DTS)](//git.dpdk.org/tools/dts/)
-- [VSPERF](//git.opnfv.org/vineperf/about/)
+- [ViNePerf](//git.opnfv.org/vineperf/about/)
 - [OvS PVP perf](//github.com/chaudron/ovs_perf/)
 - [downstream projects](//www.dpdk.org/ecosystem/#projects)