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(92386) [PATCH-V2] config/arm: restore support for Qualcomm servers
Date: 03 May 2021 03:48:31 -0700	[thread overview]
Message-ID: <613e7c$csk0n9@orsmga008-auth.jf.intel.com> (raw)

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


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

_Testing PASS_

Submitter: Thierry Herbelot <thierry.herbelot@6wind.com>
Date: 2021-04-29 08:06:44
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-03 10:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 10:48 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-06  7:25 sys_stv
2021-05-06  4:29 sys_stv
2021-05-06  0:06 sys_stv
2021-05-05 20:17 sys_stv
2021-05-05 18:14 sys_stv
2021-05-05 16:36 sys_stv
2021-05-05 14:02 sys_stv
2021-05-05 10:19 sys_stv
2021-05-05  8:41 sys_stv
2021-05-05  6:01 sys_stv
2021-05-04 16:31 sys_stv
2021-05-04 14:54 sys_stv
2021-05-04 10:19 sys_stv
2021-05-04  2:57 sys_stv
2021-05-03 17:27 sys_stv
2021-05-03 12:51 sys_stv
2021-05-03  7:18 sys_stv
2021-05-02  5:12 sys_stv
2021-05-01 21:25 sys_stv
2021-05-01 18:47 sys_stv
2021-05-01  5:22 sys_stv
2021-05-01  2:55 sys_stv
2021-05-01  0:53 sys_stv
2021-04-30 22:51 sys_stv
2021-04-30 20:48 sys_stv
2021-04-30 18:45 sys_stv
2021-04-30 15:28 sys_stv
2021-04-30  9:13 sys_stv
2021-04-30  2:56 sys_stv
2021-04-30  0:04 sys_stv
2021-04-29 21:12 sys_stv
2021-04-29 17:55 sys_stv
2021-04-29 15:27 sys_stv
2021-04-29 12:59 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$csk0n9@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).