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(106659) sid(21414) job(PER_PATCH_BUILD946-20220128191631) [v1] doc: update FIPS docs
Date: 08 Feb 2022 08:48:58 -0800	[thread overview]
Message-ID: <746b4b$g3k61p@orsmga008-auth.jf.intel.com> (raw)

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


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

_Testing PASS_

Submitter: Jakub Poczatek <jakub.poczatek@intel.com>
Date: 2022-01-28 11:08:01
Branch : dpdk
CommitID: d91998ff68fe23f351523235e5f37ec679de6b65

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.3 LTS       
Kernel : 5.8.0-63-generic         
GCC : 9.3.0-17ubuntu1~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_jumbo_frames| passed|
	| pf_smoke    | test_pf_rss         | passed|
	| pf_smoke    | test_pf_tx_rx_queue | passed|
	| vf_smoke    | test_vf_jumbo_frames| passed|
	| vf_smoke    | test_vf_rss         | passed|
	| vf_smoke    | test_vf_tx_rx_queue | passed|
	| virtio_smoke| test_virtio_loopback| passed|
	| virtio_smoke| test_virtio_pvp     | passed|
	+-------------+---------------------+-------+


DPDK STV team

             reply	other threads:[~2022-02-08 16:49 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 16:48 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-12 22:56 sys_stv
2022-02-12 19:08 sys_stv
2022-02-12 13:03 sys_stv
2022-02-12  4:44 sys_stv
2022-02-11 19:38 sys_stv
2022-02-11 10:59 sys_stv
2022-02-11  9:31 sys_stv
2022-02-11  5:52 sys_stv
2022-02-11  3:38 sys_stv
2022-02-11  2:54 sys_stv
2022-02-10 22:56 sys_stv
2022-02-09 18:09 sys_stv
2022-02-09  9:53 sys_stv
2022-02-09  5:42 sys_stv
2022-02-09  4:58 sys_stv
2022-02-09  3:28 sys_stv
2022-02-09  1:43 sys_stv
2022-02-08 22:57 sys_stv
2022-02-08 22:08 sys_stv
2022-02-08 19:26 sys_stv
2022-02-08 18:38 sys_stv
2022-02-08 14:13 sys_stv
2022-02-08 11:18 sys_stv
2022-02-08  9:03 sys_stv
2022-02-08  7:33 sys_stv
2022-02-08  4:14 sys_stv
2022-02-08  3:04 sys_stv
2022-02-07 22:56 sys_stv
2022-02-07 15:48 sys_stv
2022-02-07 13:04 sys_stv
2022-02-07 10:49 sys_stv
2022-02-07  7:48 sys_stv
2022-02-07  6:35 sys_stv
2022-02-07  5:41 sys_stv
2022-02-07  2:56 sys_stv
2022-02-07  2:00 sys_stv
2022-02-06 22:56 sys_stv
2022-02-06 14:42 sys_stv
2022-02-06  3:49 sys_stv
2022-02-06  1:08 sys_stv
2022-02-05 22:56 sys_stv
2022-02-05 17:38 sys_stv
2022-02-05  0:54 sys_stv
2022-02-04 22:39 sys_stv
2022-02-04 20:24 sys_stv
2022-02-04 19:17 sys_stv
2022-02-04 18:11 sys_stv
2022-02-04 13:18 sys_stv
2022-02-04  8:11 sys_stv
2022-02-04  3:43 sys_stv
2022-02-04  1:16 sys_stv
2022-02-03 22:56 sys_stv
2022-02-03 18:38 sys_stv
2022-02-03 16:27 sys_stv
2022-02-03  9:35 sys_stv
2022-02-03  8:49 sys_stv
2022-02-03  7:36 sys_stv
2022-02-03  6:23 sys_stv
2022-02-02 22:57 sys_stv
2022-02-02 20:13 sys_stv
2022-02-02  8:38 sys_stv
2022-02-02  7:12 sys_stv
2022-02-02  6:28 sys_stv
2022-02-01 22:56 sys_stv
2022-02-01 10:23 sys_stv
2022-02-01  9:13 sys_stv
2022-01-31 22:55 sys_stv
2022-01-31 18:34 sys_stv
2022-01-31 16:20 sys_stv
2022-01-31 14:48 sys_stv
2022-01-31 12:02 sys_stv
2022-01-31 11:19 sys_stv
2022-01-31  6:03 sys_stv
2022-01-31  0:26 sys_stv
2022-01-30 22:54 sys_stv
2022-01-30 18:22 sys_stv
2022-01-29 18:28 sys_stv
2022-01-29 12:16 sys_stv
2022-01-29 10:47 sys_stv
2022-01-29  9:57 sys_stv
2022-01-29  9:11 sys_stv
2022-01-29  7:36 sys_stv
2022-01-29  6:37 sys_stv
2022-01-29  4:05 sys_stv
2022-01-29  3:13 sys_stv
2022-01-29  1:23 sys_stv
2022-01-28 22:54 sys_stv
2022-01-28 18:28 sys_stv
2022-01-28 13:43 sys_stv
2022-01-28 12:37 sys_stv
2022-01-28 11:40 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='746b4b$g3k61p@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).