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(107904) sid(21771) job(PER_PATCH_BUILD1318-20220222021707) crypto/virtio: fix out of bounds access bug
Date: 23 Feb 2022 01:26:01 -0800	[thread overview]
Message-ID: <8ea9f5$kc4vsu@fmsmga001-auth.fm.intel.com> (raw)

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


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

_Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: 2022-02-21 18:05:42
Branch : dpdk-next-crypto
CommitID: 41e5360e892857ecd04d5db2765c53635b36fffc

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-23  9:26 UTC|newest]

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