From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(108238-108239) sid(21847) job(DTS_AUTO_542) [V1, 2/2] tests/interrupt_pmd: wait for interface up
Date: 25 Feb 2022 05:08:40 -0800 [thread overview]
Message-ID: <5975f8$f5lhov@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4361 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/108239
Subject: [V1,2/2] tests/interrupt_pmd: wait for interface up
_Testing issues_
Diff:
tests/TestSuite_flow_classify_softnic.py
tests/TestSuite_flow_classify.py
tests/TestSuite_interrupt_pmd.py
DPDK:
commit ee05a93e1e6633d0fdec409faf09f12a2e05b991
Author: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tue Feb 22 09:28:17 2022 +0100
Comment: raw/cnxk_gpio: check pointer before use in self test
DTS:
commit c17f87ae7e0b10af8281373b9017ed77f0c998f3
Author: hanyingya <yingyax.han@intel.com>
Date: Thu Jan 27 10:11:41 2022 +0800
Comment: performance_thread: remove perf test suite
Test environment and result as below:
+-----------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+-----------------------+----------+---------------------------------+--------------------------------+
| flow_classify_softnic | NIC PF | not run | run |
| interrupt_pmd | NIC PF | not run | run |
| flow_classify | NIC PF | not run | run |
+-----------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/575b380295f54b6bb23f7d6b2562e7f6
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.3 LTS
Kernel: 5.8.0-51-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: 25/1/16/8/0
with_patch Total/Pass/Fail/Blocked/NA: 25/1/16/8/0
Detail test results:
+---------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+---------------------------------------------------+------------+---------------+
| flow_classify_softnic/test_ipv4_acl_hash_jump | failed | failed |
| flow_classify_softnic/test_ipv4_acl_jump | failed | failed |
| flow_classify_softnic/test_ipv6_hash_acl_jump | failed | failed |
| flow_classify_softnic/test_ipv6_acl_hash_jump | failed | failed |
| flow_classify_softnic/test_ipv4_hash_acl_jump | failed | failed |
| flow_classify_softnic/test_ipv6_addr_hash_table | failed | failed |
| flow_classify_softnic/test_ipv6_acl_table | failed | failed |
| flow_classify_softnic/test_ipv6_hash_rss_action | failed | failed |
| flow_classify_softnic/test_ipv4_addr_hash_table | failed | failed |
| flow_classify_softnic/test_ipv6_hash_jump | failed | failed |
| flow_classify_softnic/test_ipv6_5tuple_hash_table | failed | failed |
| flow_classify_softnic/test_ipv4_hash_rss_action | failed | failed |
| flow_classify_softnic/test_ipv4_hash_jump | failed | failed |
| flow_classify_softnic/test_ipv4_5tuple_hash_table | failed | failed |
| flow_classify_softnic/test_ipv6_acl_jump | failed | failed |
| flow_classify_softnic/test_ipv4_acl_table | failed | failed |
| flow_classify/test_tcp_valid_rule | blocked | blocked |
| flow_classify/test_sctp_invalid_rule | blocked | blocked |
| flow_classify/test_udp_invalid_rule | blocked | blocked |
| flow_classify/test_sctp_valid_rule | blocked | blocked |
| flow_classify/test_udp_valid_rule | blocked | blocked |
| flow_classify_softnic/test_inconsistent_rules | passed | passed |
| flow_classify/test_multiple_rules | blocked | blocked |
| interrupt_pmd/test_different_queue | blocked | blocked |
| flow_classify/test_tcp_invalid_rule | blocked | blocked |
+---------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2022-02-25 13:08 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='5975f8$f5lhov@orsmga006-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).