From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
luzhipeng <luzhipeng@cestc.cn>
Subject: |WARNING| pw124801 [PATCH] log: add timestamp for log
Date: Sun, 5 Mar 2023 13:18:05 +0000 (UTC) [thread overview]
Message-ID: <20230305131805.F3CBC60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/124801
_Testing issues_
Submitter: luzhipeng <luzhipeng@cestc.cn>
Date: Saturday, March 04 2023 03:04:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124801 --> 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
[16/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_thread.c.o'.
[17/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_hypervisor.c.o'.
[18/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_tailqs.c.o'.
[19/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_fbarray.c.o'.
[20/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_memory.c.o'.
[21/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_dynmem.c.o'.
[22/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_random.c.o'.
[23/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace.c.o'.
[24/3190] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o'.
[25/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_lcore.c.o'.
[26/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_ctf.c.o'.
[27/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_hotplug_mp.c.o'.
[28/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_trace_utils.c.o'.
[29/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.o'.
[30/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_malloc.c.o'.
[31/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_proc.c.o'.
[32/3190] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_options.c.o'.
ninja: build stopped: subcommand failed.
==== 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/25611/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-05 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-05 13:13 dpdklab
[not found] <20230304030437.706-1-luzhipeng@cestc.cn>
2023-03-04 3:06 ` checkpatch
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=20230305131805.F3CBC60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=luzhipeng@cestc.cn \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).