automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(116320) sid(24669) job(DTS_AUTO_1582) [1/1] test_plans/af_xdp_test_plan.rst: Add test plan for AF_XDP
Date: 16 Sep 2022 04:51:57 -0700	[thread overview]
Message-ID: <0ea57a$pmnu0j@fmsmga006-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/116320
Subject: [1/1] test_plans/af_xdp_test_plan.rst: Add test plan for AF_XDP

_Testing issues_

Diff:
	tests/TestSuite_af_xdp_2.py
	tests/TestSuite_af_xdp.py
	test_plans/index.rst
	test_plans/af_xdp_test_plan.rst
	test_plans/af_xdp_2_test_plan.rst

DPDK:
	commit f8f6b1c1744e12d8d6877464a613acd1231db1a1
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Mon Jul 25 22:32:06 2022 +0200
	Comment: vhost: stop using mempool for IOTLB cache

DTS:
	commit 0c15de88fb78077b4565de70a95220eb835356e1
	Author: Song Jiale <songx.jiale@intel.com>
	Date:   Wed Sep 14 09:42:50 2022 +0000
	Comment: tests/ice_flow_priority: synchronize test plans and optimization scripts


Test environment and result as below:
+--------+----------+---------------------------------+--------------------------------+
| suits  | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+--------+----------+---------------------------------+--------------------------------+
| af_xdp | CVL Only | run                             | not run                        |
+--------+----------+---------------------------------+--------------------------------+

Log path: /regression_dts/results/test/f538169f097b4f57aab2d6cfb8a4fb30

#1: UB2004-64+216_columbiaville_25g
	OS: Ubuntu 20.04.4 LTS
	Kernel: 5.8.0-45-generic
	CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
	Clang: 10.0.0-4ubuntu1


	Status: FAILURE
	Catogory: CVL Only
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 0/0/0/0/0
	with_patch Total/Pass/Fail/Blocked/NA: 8/0/8/0/0
	
	Detail test results:
	+-----------------------------------+------------+---------------+
	| suit/case                         | with_patch | without_patch |
	+-----------------------------------+------------+---------------+
	| af_xdp/test_func_shared_umem_2pmd | failed     | n/a           |
	| af_xdp/test_func_xdp_prog         | failed     | n/a           |
	| af_xdp/test_func_xdp_prog_mq      | failed     | n/a           |
	| af_xdp/test_func_shared_umem_1pmd | failed     | n/a           |
	| af_xdp/test_func_start_queue      | failed     | n/a           |
	| af_xdp/test_func_queue_count      | failed     | n/a           |
	| af_xdp/test_func_busy_budget      | failed     | n/a           |
	| af_xdp/test_func_secondary_prog   | failed     | n/a           |
	+-----------------------------------+------------+---------------+

DPDK STV team

             reply	other threads:[~2022-09-16 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 11:51 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-16 11:51 sys_stv
2022-09-16 11:50 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='0ea57a$pmnu0j@fmsmga006-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --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).