From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [PATCH] update links in testing page
Date: Thu, 6 Jan 2022 16:45:44 +0100 [thread overview]
Message-ID: <20220106154544.137177-1-thomas@monjalon.net> (raw)
- guess_git_tree.py has been renamed pw_maintainers_cli.py
- Travis has been replaced with GitHub Actions
- up-to-date VSPERF is in vineperf repository
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/testing/_index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/testing/_index.md b/content/testing/_index.md
index 739b99b..db9e032 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -73,7 +73,7 @@ like [checkpatch](//git.dpdk.org/tools/dpdk-ci/tree/tests/checkpatch.sh),
it can be run on email reception.
For most tests, the patch must be applied
-on the [right tree](//git.dpdk.org/tools/dpdk-ci/tree/tools/guess_git_tree.py)
+on the [right tree](//git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py)
after its series dependencies.
Dealing with series and dependencies is easier
via [patchwork database request](//patches.dpdk.org/api/).
@@ -106,8 +106,8 @@ The repository mirror on [GitHub](//github.com/DPDK/dpdk)
is preferred for tests integration:
- If polling for updates, better to load the GitHub mirror.
-- Some services like [Travis](//travis-ci.com/DPDK/)
-can be hooked in GitHub.
+- Some services like [GitHub Actions](//github.com/DPDK/dpdk/actions)
+can be hooked.
### Release Validation
@@ -143,6 +143,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/vswitchperf/about/)
+- [VSPERF](//git.opnfv.org/vineperf/about/)
- [OvS PVP perf](//github.com/chaudron/ovs_perf/)
- [downstream projects](//www.dpdk.org/ecosystem/#projects)
--
2.34.1
reply other threads:[~2022-01-06 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220106154544.137177-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--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).