From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw100824-100828 [PATCH] [v7, 5/5] usertools/dpdk-telemetry: provide info on available sockets
Date: Fri, 8 Oct 2021 13:51:01 -0400 (EDT) [thread overview]
Message-ID: <20211008175101.97F6C6D76C@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Test-Label: iol-spell-check-testing
Test-Status: WARNING
http://dpdk.org/patch/100828
_Testing issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, October 08 2021 17:18:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6be6690127744bb294005bfcf539508b3d5f389e
100824-100828 --> testing fail
Test environment and result as below:
+--------------+-------------+
| Environment | spell_check |
+==============+=============+
| Ubuntu 20.04 | FAIL |
+--------------+-------------+
==== 20 line log output for Ubuntu 20.04 (spell_check): ====
dpdk/doc/guides/howto/telemetry.rst:43 tpmd
dpdk/doc/guides/howto/telemetry.rst:45 tpmd
dpdk/doc/guides/howto/telemetry.rst:104 tpmd
dpdk/doc/guides/howto/telemetry.rst:106 tpmd
dpdk/doc/guides/howto/telemetry.rst:106 tpmd
dpdk/doc/guides/howto/telemetry.rst:110 tpmd
dpdk/doc/guides/howto/telemetry.rst:117 processees
dpdk/doc/guides/howto/telemetry.rst:122 tpmd
dpdk/doc/guides/howto/telemetry.rst:128 tpmd
Errors found: 9
==== End log output ====
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19249/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-10-08 17:51 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=20211008175101.97F6C6D76C@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@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).