automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Wisam Jaddo <wisamm@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw100430 [PATCH] app/flow-perf: export some configuration options
Date: Mon,  4 Oct 2021 14:50:06 -0400 (EDT)	[thread overview]
Message-ID: <20211004185006.EB3A46D535@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-spell-check-testing
Test-Status: WARNING
http://dpdk.org/patch/100430

_Testing issues_

Submitter: Wisam Jaddo <wisamm@nvidia.com>
Date: Monday, October 04 2021 12:55:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:086d426406bd3f6fac96a15bbd871c7fe714bc2d

100430 --> 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/tools/flow-perf.rst:103 meter-profile-alg
dpdk/doc/guides/tools/flow-perf.rst:105 meter-profile-alg
dpdk/doc/guides/tools/flow-perf.rst:105 srtcmp
dpdk/doc/guides/tools/flow-perf.rst:127 mbuf-cache-size
dpdk/doc/guides/tools/flow-perf.rst:130 total-mbuf-count
dpdk/doc/guides/nics/ice.rst:224 single-ended
dpdk/doc/guides/testpmd_app_ug/run_app.rst:309 flowgen-flows
Errors found: 7
==== 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/19149/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

                 reply	other threads:[~2021-10-04 18:50 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=20211004185006.EB3A46D535@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=wisamm@nvidia.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).