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,
	Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw137172-137175 [PATCH] [RFC,v4,6/6] eal: keep per-lcore p
Date: Sun, 25 Feb 2024 07:59:14 -0800 (PST)	[thread overview]
Message-ID: <65db63d2.d40a0220.47965.b88fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Sunday, February 25 2024 15:03:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137172-137175 --> 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): ====
|                                 ~~^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[32/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace.c.o'.
[33/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_vfio.c.o'.
[34/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_utils.c.o'.
[35/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_memory.c.o'.
[36/2847] Compiling C object 'lib/76b5a35@@rte_kvargs@sta/kvargs_rte_kvargs.c.o'.
[37/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_keepalive.c.o'.
[38/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_proc.c.o'.
[39/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_malloc_mp.c.o'.
[40/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_hotplug_mp.c.o'.
[41/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_ctf.c.o'.
[42/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_unix_eal_firmware.c.o'.
[43/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_unix_eal_file.c.o'.
[44/2847] Compiling C object 'lib/76b5a35@@rte_argparse@sta/argparse_rte_argparse.c.o'.
[45/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_unix_eal_filesystem.c.o'.
[46/2847] Compiling C object 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_flow.c.o'.
[47/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_interrupts.c.o'.
[48/2847] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_devargs.c.o'.
ninja: build stopped: subcommand failed.
==== 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/29252/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-25 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 15:59 dpdklab [this message]
2024-02-25 16:29 dpdklab

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=65db63d2.d40a0220.47965.b88fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mattias.ronnblom@ericsson.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).