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(114505-114507) sid(24160) job(DTS_AUTO_1369) [V1, 3/3] tests/generic_flow_api: add case fdir_wrong_parameters sync with testplan
Date: 01 Aug 2022 21:55:44 -0700	[thread overview]
Message-ID: <e2f6d4$hrdbt1@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/114507
Subject: [V1,3/3] tests/generic_flow_api: add case fdir_wrong_parameters sync with testplan

_Testing issues_

Diff:
	test_plans/generic_flow_api_test_plan.rst
	conf/test_case_checklist.json
	tests/TestSuite_generic_flow_api.py

DPDK:
	commit 72206323a5dd3182b13f61b25a64abdddfee595c
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Sat Jul 9 10:43:09 2022 +0200
	Comment: version: 22.11-rc0

DTS:
	commit 33659110602da75f0e4ee03e54a2a81e71f8ce75
	Author: Lingli Chen <linglix.chen@intel.com>
	Date:   Tue Jul 5 04:16:47 2022 -0400
	Comment: tests/distributor: modify script add novector path expect


Test environment and result as below:
+------------------+----------+--------------------------------+---------------------------------+
| suits            | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+------------------+----------+--------------------------------+---------------------------------+
| generic_flow_api | NIC PF   | run                            | not run                         |
+------------------+----------+--------------------------------+---------------------------------+

Log path: /regression_dts/results/test/a056eacda3e448e4a6e16b2a0e7e7f7a

#1: UB2004-64+216_fortville_spirit
	OS: Ubuntu 20.04.4 LTS
	Kernel: 5.11.0-37-generic
	CPU: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
	GCC: gcc (GCC) 10.3.0
	Clang: 10.0.0-4ubuntu1


	Status: FAILURE
	Catogory: NIC PF
	Target: x86_64-native-linuxapp-gcc
	without_patch Total/Pass/Fail/Blocked/NA: 27/16/2/0/9
	with_patch Total/Pass/Fail/Blocked/NA: 28/17/2/0/9
	
	Detail test results:
	+---------------------------------------------------------------+------------+---------------+
	| suit/case                                                     | with_patch | without_patch |
	+---------------------------------------------------------------+------------+---------------+
	| generic_flow_api/test_dual_vlan                               | failed     | failed        |
	| generic_flow_api/test_fdir_for_vlan                           | failed     | failed        |
	| generic_flow_api/test_fdir_for_L2_payload                     | passed     | passed        |
	| generic_flow_api/test_fdir_for_match_report                   | n/a        | n/a           |
	| generic_flow_api/test_create_different_rule_after_destroy     | passed     | passed        |
	| generic_flow_api/test_fdir_for_nvgre                          | n/a        | n/a           |
	| generic_flow_api/test_fdir_L2_mac_filter_basic_for_ipv4_other | passed     | passed        |
	| generic_flow_api/test_tunnel_filter_nvgre                     | passed     | passed        |
	| generic_flow_api/test_64_queues                               | n/a        | n/a           |
	| generic_flow_api/test_fdir_L2_mac_filter_basic_for_ipv4_udp   | passed     | passed        |
	| generic_flow_api/test_fdir_for_vxlan                          | n/a        | n/a           |
	| generic_flow_api/test_create_same_rule_after_destroy          | passed     | passed        |
	| generic_flow_api/test_fdir_for_mac_vlan                       | passed     | passed        |
	| generic_flow_api/test_n_tuple_filter                          | n/a        | n/a           |
	| generic_flow_api/test_ethertype_filter                        | passed     | passed        |
	| generic_flow_api/test_fdir_for_ipv4                           | passed     | passed        |
	| generic_flow_api/test_tunnel_filter_vxlan                     | passed     | passed        |
	| generic_flow_api/test_fdir_for_flexbytes                      | passed     | passed        |
	| generic_flow_api/test_multiple_filters_10GB                   | n/a        | n/a           |
	| generic_flow_api/test_fdir_wrong_parameters                   | passed     | n/a           |
	| generic_flow_api/test_fdir_for_ipv6                           | passed     | passed        |
	| generic_flow_api/test_fdir_L2_mac_filter_basic_for_ipv4_tcp   | passed     | passed        |
	| generic_flow_api/test_flexbytes_filter                        | n/a        | n/a           |
	| generic_flow_api/test_jumbo_frame_size                        | n/a        | n/a           |
	| generic_flow_api/test_fdir_L2_mac_filter_complex              | passed     | passed        |
	| generic_flow_api/test_fdir_L2_mac_filter_negative             | passed     | passed        |
	| generic_flow_api/test_syn_filter                              | n/a        | n/a           |
	| generic_flow_api/test_2_tuple_filter                          | passed     | passed        |
	+---------------------------------------------------------------+------------+---------------+

DPDK STV team

                 reply	other threads:[~2022-08-02  4:55 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='e2f6d4$hrdbt1@orsmga007-auth.jf.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).