automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] (Testing) |SUCCESS| pw(92356-92358) [v3, 3/3] examples/skeleton: fix check of port and core
Date: 01 May 2021 18:10:05 -0700	[thread overview]
Message-ID: <613e7c$cs1q87@orsmga008-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]


Test-Label: intel-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/92358

_Testing PASS_

Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: 2021-04-29 00:50:46
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

             reply	other threads:[~2021-05-02  1:10 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02  1:10 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-06  5:44 sys_stv
2021-05-06  3:39 sys_stv
2021-05-06  1:12 sys_stv
2021-05-05 23:42 sys_stv
2021-05-05 22:28 sys_stv
2021-05-05 19:28 sys_stv
2021-05-05 17:49 sys_stv
2021-05-05 16:11 sys_stv
2021-05-05 14:58 sys_stv
2021-05-05 13:13 sys_stv
2021-05-05 11:59 sys_stv
2021-05-05  9:54 sys_stv
2021-05-05  8:16 sys_stv
2021-05-05  7:03 sys_stv
2021-05-05  5:37 sys_stv
2021-05-05  4:23 sys_stv
2021-05-05  1:10 sys_stv
2021-05-04 23:56 sys_stv
2021-05-04 21:50 sys_stv
2021-05-04 18:36 sys_stv
2021-05-04 17:10 sys_stv
2021-05-04 15:42 sys_stv
2021-05-04 14:05 sys_stv
2021-05-04 12:51 sys_stv
2021-05-04  9:54 sys_stv
2021-05-04  8:41 sys_stv
2021-05-04  3:22 sys_stv
2021-05-04  1:10 sys_stv
2021-05-03 18:16 sys_stv
2021-05-03 16:38 sys_stv
2021-05-03 15:24 sys_stv
2021-05-03 14:04 sys_stv
2021-05-03 11:13 sys_stv
2021-05-03  9:10 sys_stv
2021-05-03  5:40 sys_stv
2021-05-03  1:09 sys_stv
2021-05-02 22:14 sys_stv
2021-05-02 20:55 sys_stv
2021-05-02 10:56 sys_stv
2021-05-02  9:29 sys_stv
2021-05-02  8:16 sys_stv
2021-05-02  4:23 sys_stv
2021-05-02  3:10 sys_stv
2021-05-01 22:14 sys_stv
2021-05-01 19:47 sys_stv
2021-05-01 17:09 sys_stv
2021-05-01  4:08 sys_stv
2021-05-01  2:06 sys_stv
2021-05-01  0:04 sys_stv
2021-04-30 22:02 sys_stv
2021-04-30 19:59 sys_stv
2021-04-30 17:56 sys_stv
2021-04-30 12:30 sys_stv
2021-04-30  8:24 sys_stv
2021-04-30  6:21 sys_stv
2021-04-30  4:09 sys_stv
2021-04-30  1:18 sys_stv
2021-04-29 22:50 sys_stv
2021-04-29 19:58 sys_stv
2021-04-29 17:06 sys_stv
2021-04-29 14:38 sys_stv
2021-04-29 12:34 sys_stv
2021-04-29 10:54 sys_stv
2021-04-29  9:04 sys_stv
2021-04-29  7:25 sys_stv
2021-04-29  6:10 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='613e7c$cs1q87@orsmga008-auth.jf.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).