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,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: |FAILURE| pw141952-141954 [PATCH] [3/3] test/bpf: add extra test cas
Date: Thu, 27 Jun 2024 13:46:05 -0700 (PDT)	[thread overview]
Message-ID: <667dcf8d.050a0220.6ea5.0c08SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627115531.1440-4-konstantin.v.ananyev@yandex.ru>

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

_Testing issues_

Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Thursday, June 27 2024 11:55:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:eeb4b1d1f491b53c3024e0a9e8839acf514122cd

141952-141954 --> testing issues

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13.3        | FAIL               |
+---------------------+--------------------+
| FreeBSD 14.1        | FAIL               |
+---------------------+--------------------+
| Windows Server 2019 | PASS               |
+---------------------+--------------------+

==== 20 line log output for FreeBSD 14.1 (dpdk_meson_compile): ====
[189/1851] Linking static target lib/librte_cfgfile.a
[190/1851] Compiling C object lib/librte_bpf.a.p/bpf_bpf_validate.c.o
FAILED: lib/librte_bpf.a.p/bpf_bpf_validate.c.o
cc -Ilib/librte_bpf.a.p -Ilib -I../lib -Ilib/bpf -I../lib/bpf -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/net -I../lib/net -Ilib/ethdev -I../lib/ethdev -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 -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.bpf -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ lib/librte_bpf.a.p/bpf_bpf_validate.c.o -MF lib/librte_bpf.a.p/bpf_bpf_validate.c.o.d -o lib/librte_bpf.a.p/bpf_bpf_validate.c.o -c ../lib/bpf/bpf_validate.c
../lib/bpf/bpf_validate.c:2386:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Werror,-Wimplicit-int]
2386 | evaluate(struct bpf_verifier *bvf)
| ^
| int
../lib/bpf/bpf_validate.c:2386:1: error: no previous prototype for function 'evaluate' [-Werror,-Wmissing-prototypes]
../lib/bpf/bpf_validate.c:2386:9: note: declare 'static' if the function is not intended to be used outside of this translation unit
2386 | evaluate(struct bpf_verifier *bvf)
|         ^
|         static
2 errors generated.
[191/1851] Generating lib/cfgfile.sym_chk with a custom command (wrapped by meson to capture output)
[192/1851] Compiling C object lib/librte_bpf.a.p/bpf_bpf_convert.c.o
[193/1851] Compiling C object lib/librte_bpf.a.p/bpf_bpf_jit_x86.c.o
[194/1851] Generating lib/ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[195/1851] Generating lib/eal.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-27 20:46 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627115531.1440-4-konstantin.v.ananyev@yandex.ru>
2024-06-27 11:33 ` |SUCCESS| pw141952-141954 [PATCH 3/3] test/bpf: add extra test cases for bpf convert qemudev
2024-06-27 11:37 ` qemudev
2024-06-27 12:00 ` |SUCCESS| pw141954 " checkpatch
2024-06-27 12:46 ` |FAILURE| " 0-day Robot
2024-06-27 14:32 ` |SUCCESS| pw141952-141954 [PATCH] [3/3] test/bpf: add extra test cas dpdklab
2024-06-27 15:39 ` dpdklab
2024-06-27 15:52 ` dpdklab
2024-06-27 16:10 ` dpdklab
2024-06-27 16:24 ` dpdklab
2024-06-27 17:08 ` dpdklab
2024-06-27 17:33 ` |WARNING| " dpdklab
2024-06-27 17:35 ` dpdklab
2024-06-27 17:38 ` dpdklab
2024-06-27 17:39 ` dpdklab
2024-06-27 17:45 ` dpdklab
2024-06-27 17:46 ` dpdklab
2024-06-27 17:49 ` dpdklab
2024-06-27 17:53 ` dpdklab
2024-06-27 18:00 ` dpdklab
2024-06-27 18:03 ` dpdklab
2024-06-27 18:09 ` dpdklab
2024-06-27 18:11 ` |SUCCESS| " dpdklab
2024-06-27 18:11 ` |WARNING| " dpdklab
2024-06-27 18:12 ` dpdklab
2024-06-27 18:19 ` |SUCCESS| " dpdklab
2024-06-27 18:27 ` |WARNING| " dpdklab
2024-06-27 18:32 ` |SUCCESS| " dpdklab
2024-06-27 18:40 ` |WARNING| " dpdklab
2024-06-27 19:44 ` |SUCCESS| " dpdklab
2024-06-27 19:53 ` dpdklab
2024-06-27 20:27 ` dpdklab
2024-06-27 20:44 ` |FAILURE| " dpdklab
2024-06-27 20:45 ` dpdklab
2024-06-27 20:46 ` dpdklab [this message]
2024-06-27 20:49 ` dpdklab
2024-06-27 20:50 ` dpdklab
2024-06-27 20:51 ` dpdklab
2024-06-27 21:05 ` |SUCCESS| " dpdklab
2024-06-27 21:21 ` |FAILURE| " dpdklab
2024-06-27 21:28 ` |SUCCESS| " dpdklab
2024-06-27 21:31 ` dpdklab
2024-06-27 21:32 ` |FAILURE| " dpdklab
2024-06-27 21:58 ` |SUCCESS| " dpdklab
2024-06-27 22:25 ` dpdklab
2024-06-27 22:46 ` dpdklab
2024-06-28  1:35 ` |FAILURE| " dpdklab
2024-06-28  1:36 ` dpdklab
2024-06-28  1:37 ` dpdklab
2024-06-28  1:40 ` dpdklab
2024-06-28  1:40 ` dpdklab
2024-06-28  1:42 ` dpdklab
2024-06-28  1:42 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:44 ` dpdklab
2024-06-28  1:44 ` dpdklab
2024-06-28  1:45 ` dpdklab
2024-06-28  1:45 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:49 ` dpdklab
2024-06-28  1:50 ` dpdklab
2024-06-28  1:51 ` dpdklab
2024-06-28  1:52 ` dpdklab
2024-06-28  1:53 ` dpdklab
2024-06-28  1:54 ` dpdklab
2024-06-28  1:55 ` dpdklab
2024-06-28  1:56 ` dpdklab
2024-06-28  1:56 ` dpdklab
2024-06-28  1:57 ` dpdklab
2024-06-28  1:58 ` dpdklab
2024-06-28  1:58 ` dpdklab
2024-06-28  1:59 ` dpdklab
2024-06-28  1:59 ` dpdklab
2024-06-28  2:00 ` dpdklab
2024-06-28  2:01 ` dpdklab
2024-06-28  2:01 ` dpdklab
2024-06-28  2:28 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:33 ` dpdklab
2024-06-28  2:34 ` dpdklab
2024-06-28  2:34 ` dpdklab
2024-06-28  2:36 ` dpdklab
2024-06-28  2:37 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:45 ` dpdklab
2024-06-28  3:52 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:54 ` dpdklab
2024-06-28  3:54 ` dpdklab
2024-06-28  3:55 ` dpdklab
2024-06-28  3:56 ` dpdklab
2024-06-28  3:56 ` dpdklab
2024-06-28  3:58 ` dpdklab
2024-06-28  3:59 ` dpdklab
2024-06-28  3:59 ` dpdklab
2024-06-28  4:00 ` dpdklab
2024-06-28  4:00 ` dpdklab
2024-06-28 13:47 ` dpdklab
2024-06-28 14:03 ` dpdklab
2024-06-29  2:57 ` |WARNING| " 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=667dcf8d.050a0220.6ea5.0c08SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=konstantin.v.ananyev@yandex.ru \
    --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).