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>,
	Vamsi Attunuru <vattunuru@marvell.com>
Subject: |FAILURE| pw126339-126342 [PATCH] [4/4] app: add testgraph application
Date: Fri, 21 Apr 2023 06:18:02 -0700 (PDT)	[thread overview]
Message-ID: <64428d0a.050a0220.4eb6b.8ce4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Friday, April 21 2023 06:02:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f34cc454df420b9b2da8deb949fb76cba058b87

126339-126342 --> testing fail

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13       | PASS               |
+------------------+--------------------+
| Ubuntu 22.04     | FAIL               |
+------------------+--------------------+
| Debian Bullseye  | FAIL               |
+------------------+--------------------+
| Alpine           | FAIL               |
+------------------+--------------------+
| RHEL 7           | FAIL               |
+------------------+--------------------+
| openSUSE Leap 15 | FAIL               |
+------------------+--------------------+
| Debian Buster    | FAIL               |
+------------------+--------------------+
| CentOS Stream 9  | FAIL               |
+------------------+--------------------+
| Ubuntu 20.04     | FAIL               |
+------------------+--------------------+
| RHEL8            | FAIL               |
+------------------+--------------------+
| CentOS Stream 8  | FAIL               |
+------------------+--------------------+

==== 20 line log output for CentOS Stream 8 (dpdk_meson_compile): ====
[3016/3249] Compiling C object 'app/a172ced@@dpdk-test-flow-perf@exe/test-flow-perf_items_gen.c.o'.
[3017/3249] Compiling C object 'app/a172ced@@dpdk-test-flow-perf@exe/test-flow-perf_main.c.o'.
[3018/3249] Linking target app/dpdk-test-flow-perf.
[3019/3249] Compiling C object 'app/a172ced@@dpdk-test-graph@exe/test-graph_cmdline.c.o'.
[3020/3249] Compiling C object 'app/a172ced@@dpdk-test-graph@exe/test-graph_cmdline_graph.c.o'.
[3021/3249] Compiling C object 'app/a172ced@@dpdk-test-graph@exe/test-graph_parameters.c.o'.
[3022/3249] Compiling C object 'app/a172ced@@dpdk-test-graph@exe/test-graph_testgraph.c.o'.
[3023/3249] Linking target app/dpdk-test-graph.
FAILED: app/dpdk-test-graph
cc  -o app/dpdk-test-graph 'app/a172ced@@dpdk-test-graph@exe/test-graph_cmdline.c.o' 'app/a172ced@@dpdk-test-graph@exe/test-graph_cmdline_graph.c.o' 'app/a172ced@@dpdk-test-graph@exe/test-graph_parameters.c.o' 'app/a172ced@@dpdk-test-graph@exe/test-graph_testgraph.c.o' -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -Wl,--no-as-needed -pthread -Wl,--start-group -lm -ldl -lnuma lib/librte_ethdev.so.23.2 lib/librte_eal.so.23.2 lib/librte_kvargs.so.23.2 lib/librte_telemetry.so.23.2 lib/librte_net.so.23.2 lib/librte_mbuf.so.23.2 lib/librte_mempool.so.23.2 lib/librte_ring.so.23.2 lib/librte_meter.so.23.2 lib/librte_cmdline.so.23.2 lib/librte_graph.so.23.2 lib/librte_pcapng.so.23.2 lib/librte_node.so.23.2 lib/librte_lpm.so.23.2 lib/librte_hash.so.23.2 lib/librte_rcu.so.23.2 lib/librte_cryptodev.so.23.2 -Wl,--end-group '-Wl,-rpath,$ORIGIN/../lib:XXXXXXXXXXXXXXXXX' -Wl,-rpath-link,/home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-Meson@3/dpdk/build/lib
app/a172ced@@dpdk-test-graph@exe/test-graph_testgraph.c.o: In function `configure_graph_nodes':
testgraph.c:(.text+0x1252): undefined reference to `punt_kernel_node_get'
testgraph.c:(.text+0x1481): undefined reference to `ethdev_rx_get_node_data_get'
testgraph.c:(.text+0x1631): undefined reference to `ethdev_rx_get_node_data_get'
testgraph.c:(.text+0x1756): undefined reference to `ethdev_rx_get_node_data_get'
testgraph.c:(.text+0x175e): undefined reference to `ethdev_rx_node_get'
testgraph.c:(.text+0x17c8): undefined reference to `ethdev_tx_node_data_get'
testgraph.c:(.text+0x17d0): undefined reference to `ethdev_tx_node_get'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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)

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

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

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-21 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 13:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-21 14:15 dpdklab
2023-04-21 10:02 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=64428d0a.050a0220.4eb6b.8ce4SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.com \
    /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).