automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: roretzla@linux.microsoft.com
Subject: |SUCCESS|dpdk|7e06c0de19| intel-Functional
Date: 29 Apr 2024 11:09:21 -0700	[thread overview]
Message-ID: <f7b9f4$peqbs@orviesa007-auth.jf.intel.com> (raw)

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


Test-Label: intel-Functional
Test-Status: SUCCESS
_Functional PASS_

DPDK git repo: dpdk
commit 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
Author: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date:   Mon Apr 15 13:03:23 2024 -0700

    examples: move alignment attribute on types for MSVC
    
    Move location of __rte_aligned(a) to new conventional location. The new
    placement between {struct,union} and the tag allows the desired
    alignment to be imparted on the type regardless of the toolchain being
    used for both C and C++. Additionally, it avoids confusion by Doxygen
    when generating documentation.
    
    Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
    Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
    Acked-by: Morten Brørup <mb@smartsharesystems.com>
    Acked-by: Akhil Goyal <gakhil@marvell.com>

Smoke-Testing Summary : 31 Case Done, 31 Successful, 0 Failures      


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|
	+-----------------+---------------------------------------------------+-------+
	| 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_dual_vlan_priority_rxtx                      | 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:[~2024-04-29 18:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 18:09 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15 18:08 sys_stv
2024-05-14 18:09 sys_stv
2024-05-13 18:09 sys_stv
2024-05-12 18:09 sys_stv
2024-05-11 18:09 sys_stv
2024-05-10 18:09 sys_stv
2024-05-09 18:09 sys_stv
2024-05-08 18:09 sys_stv
2024-05-07 18:30 sys_stv
2024-05-06 18:08 sys_stv
2024-05-05 18:09 sys_stv
2024-05-04 18:09 sys_stv
2024-05-03 18:08 sys_stv
2024-05-02 18:08 sys_stv
2024-05-01 18:09 sys_stv
2024-04-30 18:09 sys_stv
2024-04-28 18:08 sys_stv
2024-04-27 18:09 sys_stv
2024-04-26 18:09 sys_stv
2024-04-25 18:16 sys_stv
2024-04-24 18:08 sys_stv
2024-04-23 18:08 sys_stv
2024-04-22 18:09 sys_stv
2024-04-21 18:08 sys_stv
2024-04-20 18:09 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='f7b9f4$peqbs@orviesa007-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=roretzla@linux.microsoft.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).