From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |SUCCESS| pw(121722-121727) sid(26437) job(DTS_AUTO_2306) [V1, 6/6] tests/multiprocess: Separated performance cases
Date: 09 Jan 2023 00:42:30 -0800 [thread overview]
Message-ID: <510f81$ljg3sr@fmsmga004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Test-Label: Intel-dts-pylama-test
Test-Status: SUCCESS
http://dpdk.org/patch/121727
Subject: [V1,6/6] tests/multiprocess: Separated performance cases
_Testing OK_
Diff:
tests/TestSuite_perf_efd.py
tests/TestSuite_efd.py
test_plans/perf_efd_test_plan.rst
test_plans/efd_test_plan.rst
tests/TestSuite_perf_l2fwd.py
tests/TestSuite_l2fwd.py
test_plans/perf_l2fwd_test_plan.rst
test_plans/l2fwd_test_plan.rst
tests/TestSuite_tso.py
tests/TestSuite_perf_tso.py
test_plans/tso_test_plan.rst
test_plans/perf_tso_test_plan.rst
tests/TestSuite_vxlan.py
tests/TestSuite_perf_vxlan.py
test_plans/vxlan_test_plan.rst
test_plans/perf_vxlan_test_plan.rst
tests/TestSuite_perf_ipfrag.py
tests/TestSuite_ipfrag.py
test_plans/perf_ipfrag_test_plan.rst
test_plans/ipfrag_test_plan.rst
tests/TestSuite_perf_multiprocess.py
tests/TestSuite_multiprocess.py
test_plans/perf_multiprocess_test_plan.rst
test_plans/multiprocess_test_plan.rst
test_plans/index.rst
DPDK:
commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 13 16:07:10 2022 +0100
Comment: ci: drop Travis configuration
DTS:
commit f0eb201864786a632fa93e7215b1c789e7b9f7b9
Author: Wei Ling <weix.ling@intel.com>
Date: Wed Jan 4 13:32:57 2023 +0800
Comment: tests/virtio_user_for_container_networking: modify hard code
DPDK STV team
next reply other threads:[~2023-01-09 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 8:42 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 9:19 sys_stv
2023-01-09 9:18 sys_stv
2023-01-09 8:43 sys_stv
2023-01-09 8:41 sys_stv
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='510f81$ljg3sr@fmsmga004-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@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).