From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(121422-121423) sid(26301) job(DTS_AUTO_2199) [V1, 2/2] test_plans/ice_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: add 9 subcase
Date: 28 Dec 2022 04:32:17 -0800 [thread overview]
Message-ID: <8251fc$kdtier@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/121423
Subject: [V1,2/2] test_plans/ice_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: add 9 subcase
_Testing issues_
Diff:
tests/TestSuite_ice_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py
test_plans/ice_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
DPDK:
commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 13 16:07:10 2022 +0100
Comment: ci: drop Travis configuration
DTS:
commit c3e48167b5dcb11996a5af5e203d758a9ad4bfaf
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Thu Dec 22 14:47:00 2022 +0800
Comment: framework: fix umount ahead of mount
Test environment and result as below:
+---------------------------------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------------------------------+----------+---------------------------------+--------------------------------+
| ice_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp | CVL Only | run | not run |
+---------------------------------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/ff86dad354fa43f0b600fcedd866d5bd
Detail execution results:
There were no deltas reported. There may have been an issue with the test harness.
DPDK STV team
reply other threads:[~2022-12-28 12:32 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='8251fc$kdtier@orsmga001-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).