From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] (Testing) |SUCCESS| pw(92382-92385) [v2, 4/4] vhost: fix offload flags in Rx path
Date: 30 Apr 2021 12:34:56 -0700 [thread overview]
Message-ID: <08e18f$clel3t@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Test-Label: intel-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/92385
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: 2021-04-29 08:04:35
Branch : dpdk
CommitID: 1b593b9c832e9b284cc59665fe662242a3fc1daf
Testing Summary : 8 Case Done, 8 Successful, 0 Failures
TestPlan:
pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test.rst
vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test.rst
virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst
TestSuite:
pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
OS : Ubuntu 20.04.2 LTS
Kernel : 5.8.0-48-generic
GCC : 10.2.0-5ubuntu1~20.04
NIC : Ethernet Controller E810-C for SFP
Target : x86_64-native-linuxapp-gcc
Test result details:
+-------------+---------------------+-------+
| suite | case | status|
+-------------+---------------------+-------+
| pf_smoke | test_pf_tx_rx_queue | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_jumbo_frames| passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_jumbo_frames| passed|
| virtio_smoke| test_virtio_pvp | passed|
| virtio_smoke| test_virtio_loopback| passed|
+-------------+---------------------+-------+
DPDK STV team
next reply other threads:[~2021-04-30 19:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 19:34 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-06 6:59 sys_stv
2021-05-04 2:23 sys_stv
2021-05-03 17:02 sys_stv
2021-05-03 12:26 sys_stv
2021-05-03 10:24 sys_stv
2021-05-03 6:53 sys_stv
2021-05-02 10:18 sys_stv
2021-05-02 4:47 sys_stv
2021-05-01 21:01 sys_stv
2021-05-01 18:22 sys_stv
2021-05-01 5:46 sys_stv
2021-05-01 3:44 sys_stv
2021-05-01 1:42 sys_stv
2021-04-30 23:40 sys_stv
2021-04-30 21:37 sys_stv
2021-04-30 17:07 sys_stv
2021-04-30 11:41 sys_stv
2021-04-30 8:00 sys_stv
2021-04-30 4:34 sys_stv
2021-04-30 1:43 sys_stv
2021-04-29 22:26 sys_stv
2021-04-29 19:34 sys_stv
2021-04-29 16:41 sys_stv
2021-04-29 14:13 sys_stv
2021-04-29 11:44 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='08e18f$clel3t@fmsmga008-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--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).