automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] (Smoke) |SUCCESS| pw(126815) sid(27974) job(PER_PATCH_BUILD7324-20230511163130) [v2] eventdev: avoid non-burst shortcut for variable-size bursts
Date: 12 May 2023 06:53:21 -0700	[thread overview]
Message-ID: <89f00f$kujpvq@fmsmga007-auth.fm.intel.com> (raw)

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


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

_Functional PASS_

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

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


OS : Ubuntu 20.04.5 LTS       
Kernel : 5.4.0-135-generic         
GCC : 9.4.0-1ubuntu1~20.04.1        
NIC : Ethernet Controller XL710 for 40GbE QSFP+         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-----------------+---------------------------------------------------+-------+
	| suite           | case                                              | status|
	+-----------------+---------------------------------------------------+-------+
	| checksum_offload| test_checksum_offload_with_vlan                   | passed|
	| checksum_offload| test_do_not_insert_checksum_on_the_transmit_packet| passed|
	| checksum_offload| test_hardware_checksum_check_ip_rx                | passed|
	| checksum_offload| test_hardware_checksum_check_ip_tx                | passed|
	| checksum_offload| test_hardware_checksum_check_l4_rx                | passed|
	| checksum_offload| test_hardware_checksum_check_l4_tx                | passed|
	| checksum_offload| test_insert_checksum_on_the_transmit_packet       | passed|
	| checksum_offload| test_rx_checksum_valid_flags                      | passed|
	| dual_vlan       | test_vlan_filter_config                           | passed|
	| dual_vlan       | test_vlan_filter_table                            | passed|
	| dual_vlan       | test_vlan_insert_config                           | passed|
	| dual_vlan       | test_vlan_random_test                             | passed|
	| dual_vlan       | test_vlan_strip_config                            | passed|
	| dual_vlan       | test_vlan_synthetic_test                          | passed|
	| dual_vlan       | test_vlan_tpid_config                             | passed|
	| dual_vlan       | test_vlan_stripq_config                           | n/a   |
	| jumboframes     | test_jumboframes_bigger_jumbo                     | passed|
	| jumboframes     | test_jumboframes_jumbo_jumbo                      | passed|
	| jumboframes     | test_jumboframes_jumbo_nojumbo                    | passed|
	| jumboframes     | test_jumboframes_normal_jumbo                     | passed|
	| jumboframes     | test_jumboframes_normal_nojumbo                   | passed|
	| rxtx_offload    | test_rxoffload_port_all                           | passed|
	| rxtx_offload    | test_rxoffload_port_cmdline                       | passed|
	| rxtx_offload    | test_txoffload_port                               | passed|
	| rxtx_offload    | test_txoffload_port_all                           | passed|
	| rxtx_offload    | test_txoffload_port_checksum                      | passed|
	| rxtx_offload    | test_txoffload_port_cmdline                       | passed|
	| rxtx_offload    | test_txoffload_port_multi_segs                    | passed|
	| rxtx_offload    | test_txoffload_queue                              | passed|
	| rxtx_offload    | test_rxoffload_queue                              | n/a   |
	+-----------------+---------------------------------------------------+-------+


DPDK STV team

             reply	other threads:[~2023-05-12 13:53 UTC|newest]

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