automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: David Marchand <david.marchand@redhat.com>,
	Michael Baum <michaelba@nvidia.com>,
	test-report@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Cc: daxuex.gao@intel.com, chenyux.huang@intel.com, lijuan.tu@intel.com
Subject: [dpdk-test-report]|FAILURE | dpdk|5d25466781| Intel-Testing
Date: 09 Jun 2023 16:18:17 -0700	[thread overview]
Message-ID: <d7bc6d$m20pet@orsmga008-auth.jf.intel.com> (raw)

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


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

DPDK git repo: dpdk

commit 5d254667810fffe59190ca208a078bcb666a2a71
Author: Michael Baum <michaelba@nvidia.com>
Date:   Wed May 24 00:31:53 2023 +0300

    doc: fix format in flow API guide
    
    The modify field action description inside "Generic flow API (rte_flow)"
    documentation, lists all operations supported for a destination field.
    In addition, it lists the values supported for a encapsulation level
    field.
    Before the lists, in both cases, miss a blank line causing them to look
    regular text lines.
    This patch adds the blank lines.
    
    The asynchronous operations description inside "Generic flow API
    (rte_flow)" documentation, adds some bullets to describe asynchronous
    operations behavior.
    Before the first bullet, miss a blank line causing it to look a regular
    text line.
    This patch adds the blank line.
    
    The RSS action description inside "Generic flow API (rte_flow)"
    documentation, lists the values supported for a encapsulation level
    field.
    For "2" value, it uses 3 spaces as an indentation instead of 2 after
    line breaking, causing the first line to be bold.
    This patch updates the number of spaces in the indentation.
    
    Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
    Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
    Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
    Cc: stable@dpdk.org
    
    Signed-off-by: Michael Baum <michaelba@nvidia.com>
    Acked-by: Ori Kam <orika@nvidia.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-06-09 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 23:18 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 17:41 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='d7bc6d$m20pet@orsmga008-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=chenyux.huang@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=daxuex.gao@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=michaelba@nvidia.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).