automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, abailey@iol.unh.edu
Cc: daxuex.gao@intel.com
Subject: |FAILURE|dpdk-next-dts|b71d7bdf2b| Intel-Testing
Date: 23 Sep 2025 14:18:22 -0700	[thread overview]
Message-ID: <7b7dee$588rpv@orviesa009-auth.jf.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-dts
commit b71d7bdf2b663f9fedc1d344b81a8cf65518026c
Author: Andrew Bailey <abailey@iol.unh.edu>
Date:   Wed Sep 10 08:27:49 2025 -0400

    dts: automate port binding on the TG
    
    Currently, DTS will not attempt to bind the TG interfaces to the kernel
    driver automatically, meaning the user must manually verify the TG
    binding before running DTS. Also, when the TG And DPDK drivers are the
    same, DTS does not automatically attempt to bring up the link on the TG
    port. So, this change automates binding the TG interface and bringing up
    the link, offloading this responsibility from the DTS user.
    
    Leverage TG runtime environment to bind TG ports to correct drivers
    before and after running DTS.
    
    Signed-off-by: Andrew Bailey <abailey@iol.unh.edu>
    Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
    Reviewed-by: Patrick Robb <probb@iol.unh.edu>

Testing Summary : 18 Case Done, 17 Successful, 1 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| 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           | 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| 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:[~2025-09-23 21:18 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='7b7dee$588rpv@orviesa009-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=abailey@iol.unh.edu \
    --cc=daxuex.gao@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).