automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, manish.kurup@broadcom.com
Cc: daxuex.gao@intel.com
Subject: |FAILURE|dpdk-next-net-brcm|1d627ea13a| Intel-Testing
Date: 15 Oct 2025 11:29:08 -0700	[thread overview]
Message-ID: <49ed3a$5hriok@orviesa004-auth.jf.intel.com> (raw)

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


Test-Label: intel-Testing
Test-Status: FAILURE
_Testing issues_

DPDK git repo: dpdk-next-net-brcm
commit ead4f33f4bf82eeb72f2c81dd510622a18ab2d62
Author: Manish Kurup <manish.kurup@broadcom.com>
Date:   Wed Oct 15 05:00:24 2025 -0400

    net/bnxt/tf_ulp: remove Truflow DEBUG code
    
    This commit cleans up TruFlow debug/non-production prints
    
    Signed-off-by: Manish Kurup <manish.kurup@broadcom.com>
    Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

Testing Summary : 18 Case Done, 3 Successful, 15 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.5 LTS       
Kernel : 6.8.0-40-generic         
GCC : 11.4.0-1ubuntu1~22.04.2        
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| FAILED |
	| pf_smoke    | test_pf_jumbo_frames      | FAILED |
	| pf_smoke    | test_pf_rss               | FAILED |
	| pf_smoke    | test_pf_tx_rx_queue       | FAILED |
	| vf_smoke    | test_vf_jumbo_frames      | blocked|
	| vf_smoke    | test_vf_rss               | blocked|
	| vf_smoke    | test_vf_tx_rx_queue       | blocked|
	| virtio_smoke| test_virtio_loopback      | FAILED |
	| virtio_smoke| test_virtio_pvp           | FAILED |
	+-------------+---------------------------+--------+


OS : Ubuntu 22.04.5 LTS       
Kernel : 5.15.0-119-generic         
GCC : 11.4.0-1ubuntu1~22.04.2        
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| FAILED|
	| pf_smoke    | test_pf_jumbo_frames      | FAILED|
	| pf_smoke    | test_pf_rss               | FAILED|
	| pf_smoke    | test_pf_tx_rx_queue       | FAILED|
	| vf_smoke    | test_vf_jumbo_frames      | FAILED|
	| vf_smoke    | test_vf_rss               | FAILED|
	| vf_smoke    | test_vf_tx_rx_queue       | FAILED|
	| virtio_smoke| test_virtio_loopback      | FAILED|
	| virtio_smoke| test_virtio_pvp           | FAILED|
	+-------------+---------------------------+-------+


DPDK STV team

                 reply	other threads:[~2025-10-15 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='49ed3a$5hriok@orviesa004-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=manish.kurup@broadcom.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).