From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: web@dpdk.org
Subject: [PATCH] web: updated ci testing information
Date: Thu, 15 Dec 2022 09:14:21 -0500 [thread overview]
Message-ID: <20221215141421.10065-1-lylavoie@iol.unh.edu> (raw)
* 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(-)
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)
--
2.38.1
next reply other threads:[~2022-12-15 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:14 Lincoln Lavoie [this message]
2023-01-13 14:05 ` Thomas Monjalon
2023-02-27 15:34 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221215141421.10065-1-lylavoie@iol.unh.edu \
--to=lylavoie@iol.unh.edu \
--cc=web@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).