automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |WARNING| pw135872 [PATCH] eal: refactor rte_eal_init into sub-funct
Date: Tue, 16 Jan 2024 14:50:00 -0800 (PST)	[thread overview]
Message-ID: <65a70818.920a0220.b62e3.14d7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/135872

_Testing issues_

Submitter: Rahul Gupta <rahulgupt@linux.microsoft.com>
Date: Monday, January 15 2024 08:50:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135872 --> testing fail

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN                 |
+--------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
build/examples/dpdk-fips_validation [EAL options] --
--req-file: REQUEST-FILE-PATH
--rsp-file: RESPONSE-FILE-PATH
--path-is-folder: indicating both paths are folders
--mbuf-dataroom: mbuf dataroom size (default 65279 bytes)
--cryptodev: CRYPTODEV-NAME
--cryptodev-id: CRYPTODEV-ID-NAME
--self-test: self test indicator
--broken-test-id: self broken test ID
--broken-test-dir: self broken test direction
build/examples/dpdk-fips_validation [EAL options] --
--req-file: REQUEST-FILE-PATH
--rsp-file: RESPONSE-FILE-PATH
--path-is-folder: indicating both paths are folders
--mbuf-dataroom: mbuf dataroom size (default 65279 bytes)
--cryptodev: CRYPTODEV-NAME
--cryptodev-id: CRYPTODEV-ID-NAME
--self-test: self test indicator
--broken-test-id: self broken test ID
--broken-test-dir: self broken test direction
==== End log output ====

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28863/

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2024-01-16 22: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=65a70818.920a0220.b62e3.14d7SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=rahulgupt@linux.microsoft.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).