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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw146202-146203 [PATCH] [2/2] gpudev: add malloc annotatio
Date: Fri, 18 Oct 2024 18:04:11 -0700 (PDT)	[thread overview]
Message-ID: <6713058b.050a0220.1231e4.72a7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241017225844.235401-3-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/146203

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 17 2024 22:58:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fe8eba692c59a92c9308f1fe429b101b9f2377bf

146202-146203 --> testing issues

Upstream job id: Generic-VM-DPDK-Compile-Meson#30438

Test environment and result as below:

+--------------+--------------------+
| Environment  | dpdk_meson_compile |
+==============+====================+
| FreeBSD 13.4 | FAIL               |
+--------------+--------------------+
| FreeBSD 14.1 | FAIL               |
+--------------+--------------------+

==== 20 line log output for FreeBSD 14.1 (dpdk_meson_compile): ====
[1613/1856] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_actions_gen.c.o
[1614/1856] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_items_gen.c.o
[1615/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_ml_test.c.o
[1616/1856] Linking target app/dpdk-test-fib
[1617/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_parser.c.o
[1618/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_ml_main.c.o
[1619/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_test_common.c.o
[1620/1856] Compiling C object app/dpdk-test-gpudev.p/test-gpudev_main.c.o
FAILED: app/dpdk-test-gpudev.p/test-gpudev_main.c.o
cc -Iapp/dpdk-test-gpudev.p -Iapp -I../app -Ilib/gpudev -I../lib/gpudev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/freebsd/include -I../lib/eal/freebsd/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/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/meter -I../lib/meter -fdiagnostics-color=always -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-missing-field-initializers -D_
 GNU_SOURCE -D__BSD_VISIBLE -march=native -mrtm -DALLOW_EXPERIMENTAL_API -MD -MQ app/dpdk-test-gpudev.p/test-gpudev_main.c.o -MF app/dpdk-test-gpudev.p/test-gpudev_main.c.o.d -o app/dpdk-test-gpudev.p/test-gpudev_main.c.o -c ../app/test-gpudev/main.c
../app/test-gpudev/main.c:103:32: error: unknown warning group '-Wuse-after-free', ignored [-Werror,-Wunknown-warning-option]
103 | #pragma GCC diagnostic ignored "-Wuse-after-free"
|                                ^
1 error generated.
[1621/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_test_device_ops.c.o
[1622/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_ml_options.c.o
[1623/1856] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_main.c.o
[1624/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_test_model_common.c.o
[1625/1856] Compiling C object app/dpdk-test-mldev.p/test-mldev_test_model_ops.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-19  1:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241017225844.235401-3-stephen@networkplumber.org>
2024-10-17 22:31 ` |SUCCESS| pw146202-146203 [PATCH 2/2] gpudev: add malloc annotations to rte_gpu_mem_alloc qemudev
2024-10-17 22:35 ` qemudev
2024-10-17 23:00 ` |SUCCESS| pw146203 " checkpatch
2024-10-18  0:02 ` |FAILURE| " 0-day Robot
2024-10-18 11:58 ` |SUCCESS| pw146202-146203 [PATCH] [2/2] gpudev: add malloc annotatio dpdklab
2024-10-18 12:12 ` dpdklab
2024-10-18 12:18 ` dpdklab
2024-10-18 12:23 ` dpdklab
2024-10-18 21:40 ` dpdklab
2024-10-19  0:59 ` |FAILURE| " dpdklab
2024-10-19  1:04 ` dpdklab [this message]
2024-10-19  1:05 ` dpdklab
2024-10-19  1:58 ` |PENDING| " dpdklab
2024-10-19  5:33 ` |FAILURE| " dpdklab
2024-10-19  5:50 ` dpdklab
2024-10-19  5:53 ` dpdklab
2024-10-19  6:28 ` dpdklab
2024-10-19  7:42 ` dpdklab
2024-10-19  7:43 ` dpdklab
2024-10-19  7:44 ` dpdklab
2024-10-21 23:50 ` |WARNING| " dpdklab
2024-10-23  8:10 ` |FAILURE| " 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=6713058b.050a0220.1231e4.72a7SMTPIN_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).