From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw138754-138762 [PATCH] [v11,9/9] log: colorize log output
Date: Sat, 23 Mar 2024 20:49:29 -0700 (PDT) [thread overview]
Message-ID: <65ffa2c9.050a0220.3231b.7966SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240324024109.306614-10-stephen@networkplumber.org>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138762
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sunday, March 24 2024 02:33:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0219d467bcb1d19b386b5bae8eecd3514ba13fdb
138754-138762 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 11 (arm) | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | FAIL |
+---------------------+----------------+
==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
[1/2865] Compiling C object 'lib/76b5a35@@rte_kvargs@sta/kvargs_rte_kvargs.c.o'.
[2/2865] Compiling C object 'lib/76b5a35@@rte_argparse@sta/argparse_rte_argparse.c.o'.
[3/2865] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.o'.
[4/2865] Linking static target lib/librte_argparse.a.
[5/2865] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry_data.c.o'.
[6/2865] Linking static target lib/librte_kvargs.a.
[7/2865] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry_legacy.c.o'.
[8/2865] Linking static target lib/librte_telemetry.a.
[9/2865] Compiling C object 'lib/76b5a35@@rte_log@sta/log_log.c.o'.
FAILED: lib/76b5a35@@rte_log@sta/log_log.c.o
ccache cc -Ilib/76b5a35@@rte_log@sta -Ilib -I../lib -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/log -I../lib/log -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.log -MD -MQ 'lib/76b5a35@@rte_log@sta/log_log.c.o' -MF 'lib/76b5a35@@rte_log@sta/log_log.c.o.d' -o 'lib/76b5a35@@rte_log@sta/log_log.c.o' -c ../lib/
log/log.c
../lib/log/log.c: In function 'journal_send_id':
../lib/log/log.c:881:17: error: ignoring return value of 'write' declared with attribute 'warn_unused_result' [-Werror=unused-result]
881 | write(fd, syslog_id, len);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[10/2865] Generating argparse.sym_chk with a meson_exe.py custom command.
[11/2865] Generating kvargs.sym_chk with a meson_exe.py custom command.
[12/2865] Generating telemetry.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29644/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-24 3:49 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240324024109.306614-10-stephen@networkplumber.org>
2024-03-24 2:20 ` |SUCCESS| pw138754-138762 [PATCH v11 9/9] " qemudev
2024-03-24 2:24 ` qemudev
2024-03-24 2:43 ` |WARNING| pw138762 " checkpatch
2024-03-24 3:21 ` |FAILURE| pw138754-138762 [PATCH] [v11,9/9] " dpdklab
2024-03-24 3:21 ` dpdklab
2024-03-24 3:21 ` |SUCCESS| " dpdklab
2024-03-24 3:22 ` |FAILURE| " dpdklab
2024-03-24 3:22 ` dpdklab
2024-03-24 3:22 ` dpdklab
2024-03-24 3:22 ` dpdklab
2024-03-24 3:23 ` dpdklab
2024-03-24 3:23 ` dpdklab
2024-03-24 3:23 ` |SUCCESS| " dpdklab
2024-03-24 3:23 ` |FAILURE| " dpdklab
2024-03-24 3:23 ` dpdklab
2024-03-24 3:23 ` |SUCCESS| " dpdklab
2024-03-24 3:24 ` dpdklab
2024-03-24 3:24 ` dpdklab
2024-03-24 3:24 ` |FAILURE| " dpdklab
2024-03-24 3:24 ` dpdklab
2024-03-24 3:24 ` |SUCCESS| " dpdklab
2024-03-24 3:25 ` |FAILURE| " dpdklab
2024-03-24 3:25 ` dpdklab
2024-03-24 3:26 ` |SUCCESS| " dpdklab
2024-03-24 3:26 ` |FAILURE| " dpdklab
2024-03-24 3:26 ` dpdklab
2024-03-24 3:27 ` |SUCCESS| " dpdklab
2024-03-24 3:27 ` dpdklab
2024-03-24 3:28 ` |FAILURE| " dpdklab
2024-03-24 3:28 ` dpdklab
2024-03-24 3:29 ` |SUCCESS| " dpdklab
2024-03-24 3:29 ` |FAILURE| " dpdklab
2024-03-24 3:30 ` |WARNING| " dpdklab
2024-03-24 3:30 ` |SUCCESS| " dpdklab
2024-03-24 3:32 ` |FAILURE| " dpdklab
2024-03-24 3:33 ` |SUCCESS| " dpdklab
2024-03-24 3:34 ` dpdklab
2024-03-24 3:35 ` |FAILURE| " dpdklab
2024-03-24 3:35 ` |SUCCESS| " dpdklab
2024-03-24 3:35 ` |FAILURE| " dpdklab
2024-03-24 3:36 ` dpdklab
2024-03-24 3:36 ` |WARNING| " dpdklab
2024-03-24 3:36 ` |FAILURE| " dpdklab
2024-03-24 3:36 ` |SUCCESS| " dpdklab
2024-03-24 3:36 ` |FAILURE| " dpdklab
2024-03-24 3:37 ` |WARNING| " dpdklab
2024-03-24 3:37 ` |FAILURE| " dpdklab
2024-03-24 3:38 ` |SUCCESS| " dpdklab
2024-03-24 3:38 ` |WARNING| " dpdklab
2024-03-24 3:38 ` |FAILURE| " dpdklab
2024-03-24 3:38 ` |SUCCESS| " dpdklab
2024-03-24 3:39 ` dpdklab
2024-03-24 3:39 ` |FAILURE| " dpdklab
2024-03-24 3:41 ` dpdklab
2024-03-24 3:41 ` dpdklab
2024-03-24 3:41 ` dpdklab
2024-03-24 3:42 ` |SUCCESS| " dpdklab
2024-03-24 3:42 ` |FAILURE| " dpdklab
2024-03-24 3:43 ` |SUCCESS| " dpdklab
2024-03-24 3:44 ` |FAILURE| pw138762 [PATCH v11 9/9] " 0-day Robot
2024-03-24 3:46 ` |FAILURE| pw138754-138762 [PATCH] [v11,9/9] " dpdklab
2024-03-24 3:46 ` |SUCCESS| " dpdklab
2024-03-24 3:47 ` |FAILURE| " dpdklab
2024-03-24 3:49 ` dpdklab [this message]
2024-03-24 3:50 ` |SUCCESS| " dpdklab
2024-03-24 3:50 ` |FAILURE| " dpdklab
2024-03-24 3:56 ` dpdklab
2024-03-24 3:57 ` dpdklab
2024-03-24 3:58 ` dpdklab
2024-03-24 3:58 ` dpdklab
2024-03-24 3:59 ` dpdklab
2024-03-24 4:00 ` dpdklab
2024-03-24 4:01 ` dpdklab
2024-03-24 4:41 ` dpdklab
2024-03-24 4:47 ` dpdklab
2024-03-24 5:08 ` dpdklab
2024-03-24 5:10 ` dpdklab
2024-03-24 5:40 ` dpdklab
2024-03-24 6:03 ` dpdklab
2024-03-25 3:07 ` |SUCCESS| " dpdklab
2024-03-25 3:43 ` 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=65ffa2c9.050a0220.3231b.7966SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).