From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, yogesh.jangra@intel.com
Subject: [dts-test-report] |SUCCESS| pw(119555-119557) sid(25623) job(DTS_AUTO_1795) [3/3] test/softnic: updated softnic test suite as per dpdk 22.11 changes
Date: 08 Nov 2022 18:11:57 -0800 [thread overview]
Message-ID: <ea6bce$j1dbmj@fmsmga007-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: SUCCESS
http://dpdk.org/patch/119557
Subject: [3/3] test/softnic: updated softnic test suite as per dpdk 22.11 changes
_Testing OK_
Diff:
tests/TestSuite_metering_and_policing.py
test_plans/metering_and_policing_test_plan.rst
test_plans/index.rst
tests/TestSuite_flow_classify_softnic.py
test_plans/flow_classify_softnic_test_plan.rst
tests/TestSuite_softnic.py
test_plans/softnic_test_plan.rst
dep/softnic/rx_tx/rx_tx_2.io
dep/softnic/rx_tx/rx_tx_1.io
dep/softnic/rx_tx/rx_tx.spec
dep/softnic/rx_tx/rx_tx.cli
dep/softnic/rx_tx/readme.txt
dep/softnic/rx_tx/pcap_files/out.txt
dep/softnic/rx_tx/pcap_files/in.txt
DPDK:
commit a39f5e14560df310e7af3c135a11bb6f51eb92e6
Author: Rahul Bhansali <rbhansali@marvell.com>
Date: Wed May 25 14:43:27 2022 +0530
Comment: examples/l2fwd: check Rx packets count
DTS:
commit 878a9c7ea3b073956c4efc8cf21ac43454b1b336
Author: Zhimin Huang <zhiminx.huang@intel.com>
Date: Mon Oct 10 07:42:43 2022 +0800
Comment: tests/ice_dcf_qos:modify the command according to the dpdk changed
DPDK STV team
next reply other threads:[~2022-11-09 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 2:11 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-09 2:14 sys_stv
2022-11-09 2:13 sys_stv
2022-11-09 2:09 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='ea6bce$j1dbmj@fmsmga007-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yogesh.jangra@intel.com \
/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).