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, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Jie Hai <haijie1@huawei.com>
Subject: |FAILURE| pw122177-122178 [PATCH] [2/2] ring: add ring info telemetry cmd
Date: Tue, 17 Jan 2023 10:27:34 +0000 (UTC)	[thread overview]
Message-ID: <20230117102734.F3E8160096@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/122178

_Testing issues_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Tuesday, January 17 2023 09:10:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:83397b9f073904438965e1fda2efe76f7850fe01

122177-122178 --> testing fail

Test environment and result as below:

+-------------------------------+----------------+--------------+
|          Environment          | dpdk_unit_test | lpm_autotest |
+===============================+================+==============+
| Ubuntu 20.04 ARM GCC Native   | FAIL           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM Clang Native | PASS           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE          | SKIPPED        | FAIL         |
+-------------------------------+----------------+--------------+

==== 20 line log output for Ubuntu 20.04 ARM SVE (lpm_autotest): ====
[76/630] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_arm_rte_hypervisor.c.o'.
[77/630] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_arm_rte_power_intrinsics.c.o'.
[78/630] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_memalloc.c.o'.
[79/630] Compiling C object 'lib/76b5a35@@rte_ring@sta/ring_rte_ring.c.o'.
FAILED: lib/76b5a35@@rte_ring@sta/ring_rte_ring.c.o
gcc-10 -Ilib/76b5a35@@rte_ring@sta -Ilib -I../lib -Ilib/ring -I../lib/ring -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -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=armv8.2-a+crypto+sve -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.ring -MD -MQ 'lib/76b5a35@@rte_ring@sta/ring_rte_ring.c.o' -MF 'lib/76b5a35@@rte_ring@sta/ring_rte_ring.c.o.d' -o 'lib/76b5a35@@rte_ring@sta/ring_rte_ring.c.o' -c ../lib/ring/rte_ring.c
In file included from /usr/include/stdio.h:867,
from ../lib/ring/rte_ring.c:10:
In function 'snprintf',
inlined from 'ring_handle_info' at ../lib/eal/include/rte_string_fns.h:61:17:
/usr/include/aarch64-linux-gnu/bits/stdio2.h:67:10: error: '__builtin___snprintf_chk' specified bound 32 exceeds destination size 29 [-Werror=stringop-overflow=]
67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
68 |        __bos (__s), __fmt, __va_arg_pack ());
|        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[80/630] Compiling C object 'lib/76b5a35@@rte_rcu@sta/rcu_rte_rcu_qsbr.c.o'.
[81/630] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_linux_eal_vfio.c.o'.
[82/630] Compiling C object 'lib/76b5a35@@rte_mempool@sta/mempool_rte_mempool.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-01-17 10:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 10:27 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-17 11:09 dpdklab
2023-01-17 11:09 dpdklab
2023-01-17 11:07 dpdklab
2023-01-17 11:06 dpdklab
2023-01-17 11:04 dpdklab
2023-01-17 10:43 dpdklab
2023-01-17 10:42 dpdklab
2023-01-17 10:40 dpdklab
2023-01-17 10:39 dpdklab
2023-01-17 10:37 dpdklab
2023-01-17 10:36 dpdklab
2023-01-17 10:34 dpdklab
2023-01-17 10:24 dpdklab
2023-01-17  9:59 dpdklab
2023-01-17  9:54 dpdklab
2023-01-17  9:39 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=20230117102734.F3E8160096@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=haijie1@huawei.com \
    --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).