automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>, Akhil Goyal <gakhil@marvell.com>,
	daxuex.gao@intel.com, chenyux.huang@intel.com,
	lijuan.tu@intel.com
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-crypto|39d469a7eb| Intel-Testing
Date: 16 Feb 2023 00:23:21 -0800	[thread overview]
Message-ID: <649fab$lrpcuc@fmsmga008-auth.fm.intel.com> (raw)

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


Test-Label: intel-Testing
Test-Status: SUCCESS 
_Testing PASS 

DPDK git repo: dpdk-next-crypto

commit 39d469a7eb4f157923be73aea0b0cc1015860ca7
Author: Robin Jarry <rjarry@redhat.com>
Date:   Thu Feb 9 10:43:54 2023 +0100

    eal: add lcore usage telemetry endpoint
    
    Allow fetching CPU cycles usage for all lcores with a single request.
    This endpoint is intended for repeated and frequent invocations by
    external monitoring systems and therefore returns condensed data.
    
    It consists of a single dictionary with three keys: "lcore_ids",
    "total_cycles" and "busy_cycles" that are mapped to three arrays of
    integer values. Each array has the same number of values, one per lcore,
    in the same order.
    
    Example:
    
     --> /eal/lcore/usage
     {
       "/eal/lcore/usage": {
         "lcore_ids": [
           4,
           5
         ],
         "total_cycles": [
           23846845590,
           23900558914
         ],
         "busy_cycles": [
           21043446682,
           21448837316
         ]
       }
     }
    
    Signed-off-by: Robin Jarry <rjarry@redhat.com>
    Reviewed-by: Kevin Laatz <kevin.laatz@intel.com>

Testing Summary : 18 Case Done, 18 Successful, 0 Failures

Testbed #1: 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_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 20.04.5 LTS       
	  Kernel : 5.8.0-63-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  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 20.04.5 LTS       
	  Kernel : 5.13.0-30-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  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-02-16  8:23 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='649fab$lrpcuc@fmsmga008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=gakhil@marvell.com \
    --cc=lijuan.tu@intel.com \
    --cc=rjarry@redhat.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).