From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] [dts-test-report] |FAILURE| pw(93951) [V2] test_plans/metering_and_policing: modify command of adding port meter policy
Date: 07 Jun 2021 02:38:57 -0700 [thread overview]
Message-ID: <f381f8$eb4r81@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Test-Label: Intel-dts-test
Test-Status: FAILURE
http://dpdk.org/patch/93951
Subject: [V2] test_plans/metering_and_policing: modify command of adding port meter policy
_Testing issues_
Diff:
test_plans/metering_and_policing_test_plan.rst
DPDK:
commit 64307fad7d2b6af3be5e19833e404312f01f6ce5
Author: David Marchand <david.marchand@redhat.com>
Date: Thu May 6 10:27:54 2021 +0200
Comment: telemetry: remove static limit on callbacks count
DTS:
commit 3af87209c877728b730b6b00e8b84d192a7b36db
Author: Yan Xia <yanx.xia@intel.com>
Date: Thu May 20 11:41:57 2021 +0800
Comment: tests/ftag: remove TestSuite_ftag
DOC test failed information:
reading sources... [ 99%] vxlan_sample_test_plan
reading sources... [100%] vxlan_test_plan
index.rst:36: WARNING: toctree contains reference to nonexisting document u'ftag_test_plan'
index.rst:36: WARNING: toctree contains reference to nonexisting document u'pf_smoke_test'
index.rst:36: WARNING: toctree contains reference to nonexisting document u'vf_smoke_test'
looking for now-outdated files... none found
pickling environment... done
acl_test_plan.rst: WARNING: document isn't included in any toctree
pf_smoke_test_plan.rst: WARNING: document isn't included in any toctree
power_negative_test_plan.rst: WARNING: document isn't included in any toctree
vf_smoke_test_plan.rst: WARNING: document isn't included in any toctree
done
preparing documents... done
writing output... [ 0%] ABI_stable_test_plan
DPDK STV team
reply other threads:[~2021-06-07 9:39 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='f381f8$eb4r81@orsmga001-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--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).