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(110112-110113) sid(22620) job(DTS_AUTO_787) [V1, 2/2] tests/vdev_primary_secondary: add automation testcase2 sync with testplan
Date: 22 Apr 2022 03:22:59 -0700	[thread overview]
Message-ID: <7758ae$lmmi1u@orsmga005-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/110113
Subject: [V1,2/2] tests/vdev_primary_secondary: add automation testcase2 sync with testplan

_Testing issues_

Diff:
	test_plans/vdev_primary_secondary_test_plan.rst
	tests/TestSuite_vdev_primary_secondary.py

DPDK:
	commit 76076342ec8ef108a155938d46a88bb493fae60e
	Author: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
	Date:   Mon Apr 11 17:15:58 2022 +0200
	Comment: eal: emit warning for unused trylock return value

DTS:
	commit 8beb7c0f74d0d45bb55fe2a6010a38c2089c6340
	Author: Jun Dong <junx.dong@intel.com>
	Date:   Wed Apr 20 15:04:20 2022 +0800
	Comment: framework/logger: fix bug of generate the log output path

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

vdev_primary_secondary_test_plan.rst:159: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team

             reply	other threads:[~2022-04-22 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 10:22 sys_stv [this message]
2022-04-22 10:28 sys_stv

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='7758ae$lmmi1u@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).