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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Arshdeep Kaur <arshdeep.kaur@intel.com>
Subject: |FAILURE| pw116184 [PATCH] [v2] dumpcap: add the mutiprocess fileprefix support.
Date: Mon, 12 Sep 2022 13:41:04 +0000 (UTC)	[thread overview]
Message-ID: <20220912134104.9873A600AE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/116184

_Testing issues_

Submitter: Arshdeep Kaur <arshdeep.kaur@intel.com>
Date: Monday, September 12 2022 12:43:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4aee6110bb10b0225fa9562f2e48af233a9058a1

116184 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Ubuntu 18.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 32           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Fedora 31           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL 7              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 33           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34 clang     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Fedora 33 (dpdk_meson_compile): ====
[3085/3358] Generating rte_baseband_null_def with a custom command.
[3086/3358] Generating rte_baseband_null_mingw with a custom command.
[3087/3358] Compiling C object 'drivers/a715181@@tmp_rte_baseband_turbo_sw@sta/baseband_turbo_sw_bbdev_turbo_software.c.o'.
[3088/3358] Linking static target drivers/libtmp_rte_baseband_turbo_sw.a.
[3089/3358] Linking target drivers/librte_baseband_null.so.23.0.
[3090/3358] Generating rte_baseband_turbo_sw.pmd.c with a custom command.
[3091/3358] Compiling C object 'drivers/a715181@@rte_baseband_turbo_sw@sta/meson-generated_.._rte_baseband_turbo_sw.pmd.c.o'.
[3092/3358] Linking static target drivers/librte_baseband_turbo_sw.a.
[3093/3358] Compiling C object 'drivers/a715181@@rte_baseband_turbo_sw@sha/meson-generated_.._rte_baseband_turbo_sw.pmd.c.o'.
[3094/3358] Generating rte_baseband_turbo_sw_def with a custom command.
[3095/3358] Generating rte_baseband_turbo_sw_mingw with a custom command.
[3096/3358] Compiling C object 'app/a172ced@@dpdk-dumpcap@exe/dumpcap_main.c.o'.
FAILED: app/a172ced@@dpdk-dumpcap@exe/dumpcap_main.c.o
ccache cc -Iapp/a172ced@@dpdk-dumpcap@exe -Iapp -I../app -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/x86/include -I../lib/eal/x86/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/pdump -I../lib/pdump -Ilib/bpf -I../lib/bpf -Ilib/pcapng -I../lib/pcapng -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 -march=native -DALLOW_EXPERIMENTAL_API  -MD -MQ 'app/a172ced@@dpdk-dumpcap@exe/dumpcap_main.c.o' -MF 'app/a172ced@@dpdk-dumpcap@exe/dumpcap_main.c.o.d' -o 'app/a172ced@@dpdk-dumpcap@exe/dumpcap_main.c.o' -c ../app/dumpcap/main.c
../app/dumpcap/main.c: In function ‘main’:
../app/dumpcap/main.c:800:4: error: ‘strncpy’ specified bound 256 equals destination size [-Werror=stringop-truncation]
800 |    strncpy(prefix, argv[2], sizeof(prefix));
|    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-09-12 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 13:41 dpdklab [this message]
     [not found] <20220912124309.233363-1-arshdeep.kaur@intel.com>
2022-09-12 14:19 ` |FAILURE| pw116184 [PATCH v2] " 0-day Robot
  -- strict thread matches above, loose matches on Subject: below --
2022-09-12 13:46 |FAILURE| pw116184 [PATCH] [v2] " dpdklab
2022-09-12 13:27 dpdklab
2022-09-12 13:20 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=20220912134104.9873A600AE@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=arshdeep.kaur@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).