automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, junfeng.guo@intel.com
Cc: daxuex.gao@intel.com, chenyux.huang@intel.com
Subject: [dpdk-test-report] (Smoke) |FAILURE| pw(126696) sid(27928) job(PER_PATCH_BUILD7283-20230505102632) [v2] net/gve: add maintainers for GVE
Date: 06 May 2023 02:44:03 -0700	[thread overview]
Message-ID: <76a62b$nevu72@fmsmga003-auth.fm.intel.com> (raw)

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


Test-Label: intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/126696

_Functional issues_

Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: 2023-05-05 02:18:53
Branch : dpdk
CommitID: d034467249

Testing Summary : 30 Case Done, 10 Successful, 20 Failures      


OS : Ubuntu 20.04.5 LTS       
Kernel : 5.4.0-135-generic         
GCC : 9.4.0-1ubuntu1~20.04.1        
NIC : I350 Gigabit Network Connection         
Target : x86_64-native-linuxapp-gcc      

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


DPDK STV team

             reply	other threads:[~2023-05-06  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  9:44 sys_stv [this message]
2023-05-08  4: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='76a62b$nevu72@fmsmga003-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=junfeng.guo@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).