From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(101552) sid(19632) job(DTS_AUTO766) [V2] tests/iavf_fdir_gtpogr: update negative case for dpdk code change
Date: 13 Oct 2021 23:50:34 -0700 [thread overview]
Message-ID: <311d4e$illdf2@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/101552
Subject: [V2] tests/iavf_fdir_gtpogr: update negative case for dpdk code change
_SKIPPED issues_
Diff:
tests/TestSuite_iavf_fdir_gtpogre.py
test_plans/iavf_fdir_gtpogre_test_plan.rst
DPDK:
commit d75eed0fbe4b942bc6df2e2908a8b5c2c30c99aa
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed Sep 1 16:49:44 2021 -0700
Comment: mbuf: fix typo in comment
DTS:
commit b082e251348d7c20e09243a742136e6d93626fab
Author: Thinh Tran <thinhtr@linux.vnet.ibm.com>
Date: Thu Sep 30 17:20:51 2021 +0000
Comment: Framework:fix the first numa node may not be '0'
Platform 1: 10.240.183.216
OS: UB2004-64+216
Category: NIC PF | Virtio | CVL Only | NIC VF
Nic: columbiaville_25g | fortville_spirit
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
generic_flow_api_test_plan.rst:2090: WARNING: Literal block ends without a blank line; unexpected unindent.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team
reply other threads:[~2021-10-14 6:50 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='311d4e$illdf2@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).