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>,
	Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw112879-112880 [PATCH] [2/2] app/testpmd: fix GTP PSC raw processing
Date: Thu, 16 Jun 2022 13:21:47 +0000 (UTC)	[thread overview]
Message-ID: <20220616132147.066CE600DC@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-aarch64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/112880

_Testing issues_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, June 16 2022 09:34:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7342e612052ae3ec875ae018548324d29abfa9c2

112879-112880 --> testing fail

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Native            | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native          | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | FAIL               |
+----------------------------------------+--------------------+

==== 20 line log output for Ubuntu 20.04 ARM GCC Cross Compile (dpdk_meson_compile): ====
[2939/3290] Compiling C object 'app/a172ced@@dpdk-test-pipeline@exe/test-pipeline_runtime.c.o'.
[2940/3290] Linking target app/dpdk-test-pipeline.
[2941/3290] Compiling C object 'app/a172ced@@dpdk-testpmd@exe/test-pmd_5tswap.c.o'.
[2942/3290] Compiling C object 'app/a172ced@@dpdk-testpmd@exe/test-pmd_cmdline_flow.c.o'.
FAILED: app/a172ced@@dpdk-testpmd@exe/test-pmd_cmdline_flow.c.o
ccache aarch64-linux-gnu-gcc -Iapp/a172ced@@dpdk-testpmd@exe -Iapp -I../app -Iapp/test-pmd -I../app/test-pmd -Ilib/ethdev -I../lib/ethdev -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 -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Ilib/cmdline -I../lib/cmdline -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/crypto/scheduler -I../drivers/crypto/scheduler -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/reorder -I../lib/reorder -Ilib/bitratestats -I../lib/bitratestats -Ilib/metrics -I../lib/metrics -Ilib/bpf -I../lib/bpf -Ilib/gro -I../lib/gro -Ilib/gso -I../lib/gso -Ilib/latencystats -I../lib/latencystats -Ilib/pdump -I../lib/pdump -Ilib/pcapng -I../lib/pcapng -Idrivers/net/bonding -I../drivers/net/bonding -Ilib/sched -I../lib/sched -Ilib/ip_frag -I../lib/ip_frag -Ilib/hash -I../lib/hash -Idrivers/net/bnxt -I../drivers/net/bnxt -Idrivers/net/bnxt/tf_ulp -I../drivers/net/bnxt/tf_ulp -Idrivers/net/bnxt/tf_ulp/generic_templates -I../drivers/net/bnxt/tf_ulp/generic_templates -Idrivers/net/bnxt/tf_core -I../drivers/net/bnxt/tf_core -Idrivers/net/bnxt/hcapi/cfa -I../drivers/net/bnxt/hcapi/cfa -Idrivers/net/i40e -I../drivers/net/i40e -Idrivers/net/i40e/base -I../drivers/net/i40e/base -Idrivers/net/ixgbe -I../drivers/net/ixgbe -Idrivers/net/ixgbe/base -I../drivers/net/ixgbe/base -Ilib/security -I../lib/security -Idrivers/bus/dpaa -I../drivers/bus/dpaa -I../drivers/bus/dpaa/include -I../drivers/bus/dpaa/base/qbman -Idrivers/common/dpaax -I../drivers/common/dpaax -I../drivers/common/dpaax/caamflib -Ilib/eventdev -I../lib/eventdev -Ilib/timer -I../lib/timer -Idrivers/mempool/dpaa -I../drivers/mempool/dpaa -Idrivers/net/dpaa -I../drivers/net/dpaa -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 -D_GNU_SOURCE -march=armv8-a+crc -moutline-atomics -DALLOW_EXPERIMENTAL_API -Wno-deprecated-declarations  -MD -MQ 'app/a172ced@@dpdk-testpmd@exe/test-pmd_cmdline_flow.c.o' -MF 'app/a172ced@@dpdk-testpmd@exe/test-pmd_cmdline_flow.c.o.d' -o 'app/a172ced@@dpdk-testpmd@exe/test-pmd_cmdline_flow.c.o' -c ../app/test-pmd/cmdline_flow.c
In file included from /usr/aarch64-linux-gnu/include/string.h:495,
from ../app/test-pmd/cmdline_flow.c:12:
In function 'memcpy',
inlined from 'cmd_set_raw_parsed' at ../app/test-pmd/cmdline_flow.c:11039:5,
inlined from 'cmd_set_raw_cb' at ../app/test-pmd/cmdline_flow.c:11172:3:
/usr/aarch64-linux-gnu/include/bits/string_fortified.h:34:10: error: '__builtin_memcpy' forming offset 4 is out of the bounds [0, 3] of object 'hdr' with type 'struct rte_gtp_psc_generic_hdr' [-Werror=array-bounds]
34 |   return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test-pmd/cmdline_flow.c: In function 'cmd_set_raw_cb':
../app/test-pmd/cmdline_flow.c:11032:36: note: 'hdr' declared here
11032 |     struct rte_gtp_psc_generic_hdr hdr;
|                                    ^~~
cc1: all warnings being treated as errors
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 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-06-16 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 13:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-16 13:19 dpdklab
2022-06-16 11:36 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=20220616132147.066CE600DC@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=getelson@nvidia.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).