automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Jerin Jacob <jerinj@marvell.com>,
	chenyux.huang@intel.com, Ruifeng Wang <ruifeng.wang@arm.com>,
	lijuan.tu@intel.com, daxuex.gao@intel.com
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-eventdev|b6c419dde1| Intel-Testing
Date: 12 Jun 2023 23:15:11 -0700	[thread overview]
Message-ID: <76a62b$ns6le8@fmsmga003-auth.fm.intel.com> (raw)

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


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

DPDK git repo: dpdk-next-eventdev

commit b6c419dde10e9f5dec7a02098c48060a7493420c
Author: Ruifeng Wang <ruifeng.wang@arm.com>
Date:   Mon May 22 14:01:37 2023 +0800

    test/mbuf: fix crash in a forked process
    
    Access of any memory in the hugepage shared file-backed area will trigger
    an unexpected forked child process segment fault. The root cause is DPDK
    doesn't support fork model [1] (calling rte_eal_init() before fork()).
    Forked child process can't be treated as a secondary process.
    
    Hence fix it by avoiding fork and doing verification in the main process.
    
    [1] https://mails.dpdk.org/archives/dev/2018-July/108106.html
    
    Fixes: af75078fece3 ("first public release")
    Cc: stable@dpdk.org
    
    Signed-off-by: Jia He <justin.he@arm.com>
    Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
    Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

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

Testbed #1: 6 Case Done, 6 Successful, 0 Failures 
	* Test result details:
	  +---------+---------------------+-------+
	  | suite   | case                | status|
	  +---------+---------------------+-------+
	  | 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|
	  +---------+---------------------+-------+
	* 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-13  6:15 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='76a62b$ns6le8@fmsmga003-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=ruifeng.wang@arm.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).