From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, yaqi.tang@intel.com
Subject: [dts-test-report] |FAILURE| pw(129559-129561) sid(28946) job(DTS_AUTO_2717) [V1, 3/3] tests/igc_tx_timestamp: igc enable tx timestamp offloading
Date: 16 Jul 2023 07:19:36 -0700 [thread overview]
Message-ID: <ad3726$lbmgr9@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/129561
Subject: [V1,3/3] tests/igc_tx_timestamp: igc enable tx timestamp offloading
_Testing issues_
Diff:
test_plans/index.rst
test_plans/igc_tx_timestamp_test_plan.rst
tests/TestSuite_igc_tx_timestamp.py
DPDK:
commit 655eb37b18b1b0dc4d106acdf0dfedde01cfb224
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Wed Jul 12 18:40:40 2023 +0200
Comment: version: 23.07-rc3
DTS:
commit 427e7c3f37bbb1263d81c466d7a83e9193013321
Author: Hongbo Li <hongbox.li@intel.com>
Date: Fri Jun 9 18:10:20 2023 +0800
Comment: tests/iavf_package_driver_error_handle: support eal_param -a to avoid running containers
DOC test failed information:
reading sources... [ 99%] vxlan_gpe_support_in_i40e_test_plan
reading sources... [100%] vxlan_test_plan
/root/UB2004-64_216/8484a13d01dc4896b61ee719ff8a157e/dts/test_plans/igc_tx_timestamp_test_plan.rst:32: WARNING: Block quote ends without a blank line; unexpected unindent.
/root/UB2004-64_216/8484a13d01dc4896b61ee719ff8a157e/dts/test_plans/igc_tx_timestamp_test_plan.rst:88: WARNING: Literal block expected; none found.
/root/UB2004-64_216/8484a13d01dc4896b61ee719ff8a157e/dts/test_plans/igc_tx_timestamp_test_plan.rst:141: WARNING: Literal block expected; none found.
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
DPDK STV team
next reply other threads:[~2023-07-16 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 14:19 sys_stv [this message]
2023-07-16 14: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='ad3726$lbmgr9@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yaqi.tang@intel.com \
/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).