automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: Jerin Jacob <jerinj@marvell.com>,
	Shijith Thotton <sthotton@marvell.com>,
	test-report@dpdk.org
Cc: daxuex.gao@intel.com, chenyux.huang@intel.com, lijuan.tu@intel.com
Subject: [dpdk-test-report]|FAILURE | dpdk-next-eventdev|b210f15c5d| Intel-Testing
Date: 17 May 2023 07:43:06 -0700	[thread overview]
Message-ID: <76ab7d$s8bt5q@fmsmga006-auth.fm.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-eventdev

commit b210f15c5d7220234e6058cd77b41ebb9dcf436c
Author: Shijith Thotton <sthotton@marvell.com>
Date:   Thu Apr 27 11:58:17 2023 +0530

    event/cnxk: fix setting event attributes in empty get work
    
    Even when no events are dequeued, it is important to update event
    attributes as they provide valuable information for checking the work
    slot state and other attributes.
    
    Fixes: c0a9774f030d ("event/cnxk: move post-processing to separate function")
    Cc: stable@dpdk.org
    
    Signed-off-by: Shijith Thotton <sthotton@marvell.com>
    Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Testing Summary : 18 Case Done, 17 Successful, 1 Failures

Testbed #1: 9 Case Done, 8 Successful, 1 Failures 
	* Test result details:
	  +-------------+---------------------------+-------+
	  | suite       | case                      | status|
	  +-------------+---------------------------+-------+
	  | asan_smoke  | test_rxtx_with_ASan_enable| passed|
	  | pf_smoke    | test_pf_rss               | passed|
	  | pf_smoke    | test_pf_tx_rx_queue       | passed|
	  | pf_smoke    | test_pf_jumbo_frames      | FAILED|
	  | vf_smoke    | test_vf_jumbo_frames      | passed|
	  | vf_smoke    | test_vf_rss               | passed|
	  | vf_smoke    | test_vf_tx_rx_queue       | passed|
	  | virtio_smoke| test_virtio_loopback      | passed|
	  | virtio_smoke| test_virtio_pvp           | passed|
	  +-------------+---------------------------+-------+
	* Environment:
	  OS : Ubuntu 22.04.2 LTS       
	  Kernel : 5.15.0-60-generic         
	  GCC : 11.3.0-1ubuntu1~22.04        
	  NIC : Ethernet Controller E810-C for SFP         
	  Target : x86_64-native-linuxapp-gcc      

Testbed #2: 9 Case Done, 9 Successful, 0 Failures 
	* 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|
	  +-------------+---------------------------+-------+
	* Environment:
	  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      

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
	   asan_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/asan_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
	   asan_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_asan_smoke.py


DPDK STV team

                 reply	other threads:[~2023-05-17 14:43 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='76ab7d$s8bt5q@fmsmga006-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=jerinj@marvell.com \
    --cc=lijuan.tu@intel.com \
    --cc=sthotton@marvell.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).