From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(111050-111051) sid(22908) job(DTS_AUTO_1022) [V2, 2/2] tests/multiprocess_iavf: add vf multiprocess test case
Date: 12 May 2022 03:09:37 -0700 [thread overview]
Message-ID: <87f1b2$gsbk7s@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3822 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/111051
Subject: [V2,2/2] tests/multiprocess_iavf: add vf multiprocess test case
_Testing issues_
Diff:
test_plans/multiprocess_iavf_test_plan.rst
tests/TestSuite_multiprocess_iavf.py
DPDK:
commit c0c305ee9e0e7c9feca6412266a778f330d20c19
Author: David Marchand <david.marchand@redhat.com>
Date: Thu May 5 11:29:52 2022 +0200
Comment: ci: build some job with ASan
DTS:
commit e82d3bc030d87966a093852b326f6d675d65cb03
Author: Jun Dong <junx.dong@intel.com>
Date: Tue May 10 17:54:31 2022 +0800
Comment: tests/*: replace codename in test suites
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
multiprocess_iavf_test_plan.rst:427: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:452: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:456: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:472: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:476: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:494: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:505: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:505: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:516: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:531: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:540: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:540: WARNING: Inline emphasis start-string without end-string.
multiprocess_iavf_test_plan.rst:549: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:568: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:589: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:604: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:618: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:923: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:935: WARNING: Literal block expected; none found.
multiprocess_iavf_test_plan.rst:948: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
multiprocess_iavf_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:[~2022-05-12 10:09 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='87f1b2$gsbk7s@orsmga007-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).