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| pw132988-133016 [PATCH] [v3,29/29] port: make API's stable
Date: Thu, 19 Oct 2023 15:11:22 -0700 (PDT)	[thread overview]
Message-ID: <6531a98a.810a0220.6ab08.1cb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 19 2023 16:55:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce

132988-133016 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Alpine (dpdk_meson_compile): ====
[2612/2622] Linking target lib/librte_table.so.24.0.
[2613/2622] Generating symbol file 'lib/76b5a35@@rte_table@sha/librte_table.so.24.0.symbols'.
[2614/2622] Linking target lib/librte_pipeline.so.24.0.
[2615/2622] Generating symbol file 'lib/76b5a35@@rte_pipeline@sha/librte_pipeline.so.24.0.symbols'.
[2616/2622] Linking target app/dpdk-test-pipeline.
[2617/2622] Linking target drivers/librte_net_softnic.so.24.0.
[2618/2622] Linking target lib/librte_dispatcher.so.24.0.
[2619/2622] Generating symbol file 'lib/76b5a35@@rte_dispatcher@sha/librte_dispatcher.so.24.0.symbols'.
[2620/2622] Linking target lib/librte_efd.so.24.0.
[2621/2622] Generating symbol file 'lib/76b5a35@@rte_efd@sha/librte_efd.so.24.0.symbols'.
[2622/2622] Linking target app/dpdk-test.
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power.c.o: in function `test_power':
test_power.c:(.text+0x204): undefined reference to `rte_power_unset_env'
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: test_power.c:(.text+0x249): undefined reference to `rte_power_unset_env'
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: test_power.c:(.text+0x281): undefined reference to `rte_power_unset_env'
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_cpufreq.c.o: in function `test_power_caps':
test_power_cpufreq.c:(.text+0x4a): undefined reference to `rte_power_unset_env'
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: test_power_cpufreq.c:(.text+0x97): undefined reference to `rte_power_unset_env'
/usr/lib/gcc/x86_64-alpine-linux-musl/12.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_cpufreq.c.o:test_power_cpufreq.c:(.text+0x4c4): more undefined references to `rte_power_unset_env' follow
collect2: error: ld returned 1 exit status
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-19 22:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 22:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 23:46 dpdklab
2023-10-19 23:37 dpdklab
2023-10-19 23:36 dpdklab
2023-10-19 23:35 dpdklab
2023-10-19 23:05 dpdklab
2023-10-19 22:33 dpdklab
2023-10-19 22:21 dpdklab
2023-10-19 22:18 dpdklab
2023-10-19 22:12 dpdklab
2023-10-19 22:09 dpdklab
2023-10-19 22:05 dpdklab
2023-10-19 22:05 dpdklab
2023-10-19 22:05 dpdklab
2023-10-19 22:04 dpdklab
2023-10-19 22:04 dpdklab
2023-10-19 22:03 dpdklab
2023-10-19 22:03 dpdklab
2023-10-19 22:03 dpdklab
2023-10-19 22:02 dpdklab
2023-10-19 22:02 dpdklab
2023-10-19 22:02 dpdklab
2023-10-19 22:02 dpdklab
2023-10-19 21:56 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=6531a98a.810a0220.6ab08.1cb6SMTPIN_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).