automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(106332-106333) sid(21320) job(DTS_AUTO_439) [V1, 2/2] tests/loopback_virtio_user_server_mode: Modify case sync with testplan
Date: 23 Jan 2022 23:57:56 -0800	[thread overview]
Message-ID: <4c6944$kn3puq@orsmga005-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3137 bytes --]

Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/106333
Subject: [V1,2/2] tests/loopback_virtio_user_server_mode: Modify case sync with testplan

_Testing issues_

Diff:
	test_plans/loopback_virtio_user_server_mode_test_plan.rst
	tests/TestSuite_loopback_virtio_user_server_mode.py

DPDK:
	commit 8a5a91401dc23ddab1ddea3667a17a615a25077f
	Author: Stephen Hemminger <stephen@networkplumber.org>
	Date:   Thu Dec 23 11:21:58 2021 -0800
	Comment: eal/linux: log hugepage create errors with filename

DTS:
	commit 889a137919cfa520fd7d52a3c42825e3d121b45d
	Author: Wei Ling <weix.ling@intel.com>
	Date:   Fri Jan 14 16:18:49 2022 +0800
	Comment: test_plans/*:modify dpdk app name

DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan

loopback_virtio_user_server_mode_test_plan.rst:881: WARNING: Literal block expected; none found.
loopback_virtio_user_server_mode_test_plan.rst:894: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:903: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:912: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:972: WARNING: Literal block expected; none found.
loopback_virtio_user_server_mode_test_plan.rst:985: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:987: WARNING: Unexpected indentation.
loopback_virtio_user_server_mode_test_plan.rst:995: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:997: WARNING: Unexpected indentation.
loopback_virtio_user_server_mode_test_plan.rst:1008: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1058: WARNING: Literal block expected; none found.
loopback_virtio_user_server_mode_test_plan.rst:1072: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1074: WARNING: Unexpected indentation.
loopback_virtio_user_server_mode_test_plan.rst:1082: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1084: WARNING: Unexpected indentation.
loopback_virtio_user_server_mode_test_plan.rst:1092: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1094: WARNING: Unexpected indentation.
loopback_virtio_user_server_mode_test_plan.rst:1102: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1113: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1163: WARNING: Literal block expected; none found.
loopback_virtio_user_server_mode_test_plan.rst:1177: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1187: WARNING: Inconsistent literal block quoting.
loopback_virtio_user_server_mode_test_plan.rst:1197: WARNING: Inconsistent literal block quoting.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team

                 reply	other threads:[~2022-01-24  7:58 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='4c6944$kn3puq@orsmga005-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).