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(126815) sid(27974) job(PER_PATCH_BUILD7324-20230511163130) [v2] eventdev: avoid non-burst shortcut for variable-size bursts
Date: 18 May 2023 13:26:56 -0700	[thread overview]
Message-ID: <8a82d4$mrq2d9@fmsmga008-auth.fm.intel.com> (raw)

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


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

_Testing PASS_

Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: 2023-05-11 08:16:41
Branch : dpdk-next-eventdev
CommitID: 19620da5ca

Testing Summary : 18 Case Done, 18 Successful, 0 Failures      

TestPlan:
	pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
	vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.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 22.04.2 LTS       
Kernel : 5.15.0-60-generic         
GCC : 11.3.0-1ubuntu1~22.04        
NIC : Ethernet Controller E810-C for SFP         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| 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|
	+-------------+---------------------------+-------+


OS : Ubuntu 22.04.2 LTS       
Kernel : 5.15.0-60-generic         
GCC : 11.3.0-1ubuntu1~22.04        
NIC : Ethernet Controller XL710 for 40GbE QSFP+         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| 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_rss               | passed|
	| vf_smoke    | test_vf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_jumbo_frames      | n/a   |
	| virtio_smoke| test_virtio_loopback      | passed|
	| virtio_smoke| test_virtio_pvp           | passed|
	+-------------+---------------------------+-------+


DPDK STV team

             reply	other threads:[~2023-05-18 20:27 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 20:26 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-25  9:28 sys_stv
2023-05-21 23:46 sys_stv
2023-05-21 23:10 sys_stv
2023-05-20 23:09 sys_stv
2023-05-20 22:33 sys_stv
2023-05-20 22:01 sys_stv
2023-05-20 21:24 sys_stv
2023-05-20 18:46 sys_stv
2023-05-19 23:24 sys_stv
2023-05-19 21:56 sys_stv
2023-05-19 21:27 sys_stv
2023-05-19 20:30 sys_stv
2023-05-19 18:26 sys_stv
2023-05-19 17:30 sys_stv
2023-05-19 17:01 sys_stv
2023-05-19 13:30 sys_stv
2023-05-19 11:27 sys_stv
2023-05-19  9:07 sys_stv
2023-05-19  7:56 sys_stv
2023-05-19  7:16 sys_stv
2023-05-19  6:09 sys_stv
2023-05-19  5:06 sys_stv
2023-05-19  3:36 sys_stv
2023-05-19  3:11 sys_stv
2023-05-19  1:02 sys_stv
2023-05-18 23:55 sys_stv
2023-05-18 22:32 sys_stv
2023-05-18 22:01 sys_stv
2023-05-18 21:25 sys_stv
2023-05-18 18:33 sys_stv
2023-05-18 17:24 sys_stv
2023-05-18 16:35 sys_stv
2023-05-18 16:03 sys_stv
2023-05-18 15:32 sys_stv
2023-05-18 14:01 sys_stv
2023-05-18 13:26 sys_stv
2023-05-18 11:03 sys_stv
2023-05-18  9:56 sys_stv
2023-05-18  7:41 sys_stv
2023-05-18  7:11 sys_stv
2023-05-18  1:43 sys_stv
2023-05-17 22:32 sys_stv
2023-05-17 20:43 sys_stv
2023-05-17 19:00 sys_stv
2023-05-17 17:46 sys_stv
2023-05-17 16:56 sys_stv
2023-05-17 16:17 sys_stv
2023-05-17 15:32 sys_stv
2023-05-17 15:02 sys_stv
2023-05-17 14:01 sys_stv
2023-05-17 12:10 sys_stv
2023-05-17  9:46 sys_stv
2023-05-17  8:46 sys_stv
2023-05-17  8:21 sys_stv
2023-05-17  4:02 sys_stv
2023-05-17  3:02 sys_stv
2023-05-17  1:31 sys_stv
2023-05-17  0:03 sys_stv
2023-05-16 23:10 sys_stv
2023-05-16 22:40 sys_stv
2023-05-16 22:04 sys_stv
2023-05-16 21:25 sys_stv
2023-05-16 15:26 sys_stv
2023-05-16 12:41 sys_stv
2023-05-16 11:27 sys_stv
2023-05-16 10:58 sys_stv
2023-05-16 10:31 sys_stv
2023-05-16  9:31 sys_stv
2023-05-16  8:03 sys_stv
2023-05-16  7:27 sys_stv
2023-05-15 23:48 sys_stv
2023-05-15 23:12 sys_stv
2023-05-15 22:36 sys_stv
2023-05-15 22:00 sys_stv
2023-05-15 21:24 sys_stv
2023-05-15 12:01 sys_stv
2023-05-15  7:02 sys_stv
2023-05-15  5:56 sys_stv
2023-05-15  3:05 sys_stv
2023-05-15  1:30 sys_stv
2023-05-15  0:08 sys_stv
2023-05-14 21:59 sys_stv
2023-05-14 21:24 sys_stv
2023-05-13 23:10 sys_stv
2023-05-13 22:35 sys_stv
2023-05-13 21:59 sys_stv
2023-05-12 22:33 sys_stv
2023-05-12 20:05 sys_stv
2023-05-12 15:21 sys_stv
2023-05-12 12:00 sys_stv
2023-05-12  2:40 sys_stv
2023-05-11 23:44 sys_stv
2023-05-11 22:56 sys_stv
2023-05-11 22:30 sys_stv
2023-05-11 20:52 sys_stv
2023-05-11 15:32 sys_stv
2023-05-11 14:32 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='8a82d4$mrq2d9@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).