From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(109207-109208) sid(22371) job(DTS_AUTO_737) [V1, 2/2] tests/cvl_iavf_fdir_pppol2tpoudp: modify test script for more fdir action
Date: 06 Apr 2022 07:16:17 -0700 [thread overview]
Message-ID: <8ea9f5$kp2mop@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3926 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/109208
Subject: [V1,2/2] tests/cvl_iavf_fdir_pppol2tpoudp: modify test script for more fdir action
_Testing issues_
Diff:
test_plans/cvl_iavf_fdir_pppol2tpoudp_test_plan.rst
tests/TestSuite_cvl_iavf_fdir_pppol2tpoudp.py
DPDK:
commit 442876b2d8fde9b7cdf86464e8a458e3bd8dd210
Author: Elena Agostini <eagostini@nvidia.com>
Date: Mon Apr 4 14:43:52 2022 +0000
Comment: gpu/cuda: add NVIDIA A30X identifier for DPU
DTS:
commit bc927c07afd378482b7001b97619b719e3b7cb31
Author: Owen Hilyard <ohilyard@iol.unh.edu>
Date: Thu Aug 12 12:22:56 2021 -0400
Comment: ci/pylama: Added pylama config file
Test environment and result as below:
+----------------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+----------------------------+----------+--------------------------------+---------------------------------+
| cvl_iavf_fdir_pppol2tpoudp | CVL Only | not run | run |
+----------------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/bf054ba07f4f4f008a6ccde4f085e825
#1: UB2004-64+216_columbiaville_25g
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: CVL Only
Target: x86_64-native-linuxapp-gcc
without_patch Total/Pass/Fail/Blocked/NA: 18/0/18/0/0
with_patch Total/Pass/Fail/Blocked/NA: 18/0/18/0/0
Detail test results:
+------------------------------------------------------------------+------------+---------------+
| suit/case | with_patch | without_patch |
+------------------------------------------------------------------+------------+---------------+
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv6_tcp | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv6_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_l2tpv2_control | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv4_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv4_tcp | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2 | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_l2tpv2_control | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_l2tpv2 | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv6_udp_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_l2tpv2 | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv6_tcp | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv4_udp_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv4_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv6_udp_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv4_tcp | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2_ipv6_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv6_pppol2tpv2_ipv4_udp_pay | failed | failed |
| cvl_iavf_fdir_pppol2tpoudp/test_mac_ipv4_pppol2tpv2 | failed | failed |
+------------------------------------------------------------------+------------+---------------+
DPDK STV team
reply other threads:[~2022-04-06 14:28 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='8ea9f5$kp2mop@fmsmga001-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).