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,
	Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Subject: |FAILURE| pw142559-142561 [PATCH] [v1,4/4] power/amd_uncore: uncore
Date: Sat, 20 Jul 2024 10:58:17 -0700 (PDT)	[thread overview]
Message-ID: <669bfab9.050a0220.2d501.2a41SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240720165030.246294-5-sivaprasad.tummala@amd.com>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/142561

_Testing issues_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Saturday, July 20 2024 16:50:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142559-142561 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#277041

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM)                            | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | FAIL               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PEND               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM Clang)                  | PEND               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM)                        | PEND               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PEND               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang)                  | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                     | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                     | PEND               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PEND               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PEND               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PEND               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PEND               |
+----------------------------------------+--------------------+

==== 20 line log output for Fedora 38 (ARM) (dpdk_meson_compile): ====
/usr/bin/ld: test_power_cpufreq.c:(.text+0x518): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_cpufreq.c:(.text+0x534): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_cpufreq.c:(.text+0x550): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_cpufreq.c.o:test_power_cpufreq.c:(.text+0x580): more undefined references to `rte_power_get_core_ops' follow
/usr/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_intel_uncore.c.o: in function `test_power_intel_uncore':
test_power_intel_uncore.c:(.text+0x14): undefined reference to `rte_power_get_uncore_ops'
/usr/bin/ld: test_power_intel_uncore.c:(.text+0x38): undefined reference to `rte_power_get_uncore_ops'
/usr/bin/ld: test_power_intel_uncore.c:(.text+0x48): undefined reference to `rte_power_get_uncore_ops'
/usr/bin/ld: test_power_intel_uncore.c:(.text+0x6c): undefined reference to `rte_power_get_uncore_ops'
/usr/bin/ld: test_power_intel_uncore.c:(.text+0x84): undefined reference to `rte_power_get_uncore_ops'
/usr/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_intel_uncore.c.o:test_power_intel_uncore.c:(.text+0x94): more undefined references to `rte_power_get_uncore_ops' follow
/usr/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_kvm_vm.c.o: in function `test_power_kvm_vm':
test_power_kvm_vm.c:(.text+0x4c): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_kvm_vm.c:(.text+0x64): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_kvm_vm.c:(.text+0x7c): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_kvm_vm.c:(.text+0x94): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: test_power_kvm_vm.c:(.text+0xac): undefined reference to `rte_power_get_core_ops'
/usr/bin/ld: app/a172ced@@dpdk-test@exe/test_test_power_kvm_vm.c.o:test_power_kvm_vm.c:(.text+0xc4): more undefined references to `rte_power_get_core_ops' follow
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
==== End log output ====

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Ubuntu 22.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.0

Ubuntu 24.04 (ARM)
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-20 17:58 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240720165030.246294-5-sivaprasad.tummala@amd.com>
2024-07-20 16:24 ` |FAILURE| pw142559-142561 [PATCH v1 4/4] power/amd_uncore: uncore power management support for AMD EPYC processors qemudev
2024-07-20 16:53 ` |SUCCESS| pw142561 " checkpatch
2024-07-20 17:26 ` |PENDING| pw142559-142561 [PATCH] [v1,4/4] power/amd_uncore: uncore dpdklab
2024-07-20 17:30 ` |SUCCESS| " dpdklab
2024-07-20 17:32 ` |WARNING| " dpdklab
2024-07-20 17:33 ` |SUCCESS| " dpdklab
2024-07-20 17:34 ` dpdklab
2024-07-20 17:34 ` |PENDING| " dpdklab
2024-07-20 17:35 ` |SUCCESS| " dpdklab
2024-07-20 17:35 ` |WARNING| " dpdklab
2024-07-20 17:37 ` |PENDING| " dpdklab
2024-07-20 17:38 ` |SUCCESS| " dpdklab
2024-07-20 17:38 ` dpdklab
2024-07-20 17:39 ` |PENDING| " dpdklab
2024-07-20 17:39 ` |SUCCESS| " dpdklab
2024-07-20 17:40 ` |WARNING| " dpdklab
2024-07-20 17:40 ` |PENDING| " dpdklab
2024-07-20 17:41 ` dpdklab
2024-07-20 17:42 ` |FAILURE| " dpdklab
2024-07-20 17:43 ` dpdklab
2024-07-20 17:43 ` |FAILURE| pw142561 [PATCH v1 4/4] power/amd_uncore: uncore power management support for AMD EPYC processors 0-day Robot
2024-07-20 17:44 ` |PENDING| pw142559-142561 [PATCH] [v1,4/4] power/amd_uncore: uncore dpdklab
2024-07-20 17:45 ` |FAILURE| " dpdklab
2024-07-20 17:45 ` |SUCCESS| " dpdklab
2024-07-20 17:45 ` |PENDING| " dpdklab
2024-07-20 17:45 ` |WARNING| " dpdklab
2024-07-20 17:46 ` |FAILURE| " dpdklab
2024-07-20 17:46 ` |PENDING| " dpdklab
2024-07-20 17:46 ` |SUCCESS| " dpdklab
2024-07-20 17:47 ` |PENDING| " dpdklab
2024-07-20 17:47 ` |WARNING| " dpdklab
2024-07-20 17:48 ` |FAILURE| " dpdklab
2024-07-20 17:49 ` |WARNING| " dpdklab
2024-07-20 17:49 ` dpdklab
2024-07-20 17:49 ` |FAILURE| " dpdklab
2024-07-20 17:51 ` |WARNING| " dpdklab
2024-07-20 17:51 ` |SUCCESS| " dpdklab
2024-07-20 17:52 ` |PENDING| " dpdklab
2024-07-20 17:53 ` |WARNING| " dpdklab
2024-07-20 17:53 ` dpdklab
2024-07-20 17:53 ` |FAILURE| " dpdklab
2024-07-20 17:54 ` |SUCCESS| " dpdklab
2024-07-20 17:54 ` |PENDING| " dpdklab
2024-07-20 17:55 ` |SUCCESS| " dpdklab
2024-07-20 17:55 ` |PENDING| " dpdklab
2024-07-20 17:56 ` dpdklab
2024-07-20 17:57 ` |FAILURE| " dpdklab
2024-07-20 17:58 ` |WARNING| " dpdklab
2024-07-20 17:58 ` dpdklab [this message]
2024-07-20 17:58 ` |FAILURE| " dpdklab
2024-07-20 17:58 ` |WARNING| " dpdklab
2024-07-20 17:58 ` |FAILURE| " dpdklab
2024-07-20 17:59 ` |SUCCESS| " dpdklab
2024-07-20 17:59 ` |FAILURE| " dpdklab
2024-07-20 17:59 ` |PENDING| " dpdklab
2024-07-20 18:01 ` |FAILURE| " dpdklab
2024-07-20 18:03 ` dpdklab
2024-07-20 18:03 ` |WARNING| " dpdklab
2024-07-20 18:03 ` |FAILURE| " dpdklab
2024-07-20 18:04 ` |WARNING| " dpdklab
2024-07-20 18:05 ` |FAILURE| " dpdklab
2024-07-20 18:05 ` |SUCCESS| " dpdklab
2024-07-20 18:06 ` |WARNING| " dpdklab
2024-07-20 18:06 ` |PENDING| " dpdklab
2024-07-20 18:06 ` |FAILURE| " dpdklab
2024-07-20 18:06 ` dpdklab
2024-07-20 18:06 ` dpdklab
2024-07-20 18:07 ` dpdklab
2024-07-20 18:07 ` dpdklab
2024-07-20 18:07 ` dpdklab
2024-07-20 18:07 ` dpdklab
2024-07-20 18:08 ` dpdklab
2024-07-20 18:08 ` dpdklab
2024-07-20 18:08 ` dpdklab
2024-07-20 18:08 ` dpdklab
2024-07-20 18:09 ` dpdklab
2024-07-20 18:09 ` dpdklab
2024-07-20 18:09 ` |PENDING| " dpdklab
2024-07-20 18:09 ` |FAILURE| " dpdklab
2024-07-20 18:09 ` dpdklab
2024-07-20 18:09 ` dpdklab
2024-07-20 18:10 ` |WARNING| " dpdklab
2024-07-20 18:10 ` |FAILURE| " dpdklab
2024-07-20 18:10 ` dpdklab
2024-07-20 18:10 ` dpdklab
2024-07-20 18:10 ` |PENDING| " dpdklab
2024-07-20 18:12 ` dpdklab
2024-07-20 18:14 ` dpdklab
2024-07-20 18:15 ` dpdklab
2024-07-20 18:15 ` |FAILURE| " dpdklab
2024-07-20 18:15 ` dpdklab
2024-07-20 18:16 ` dpdklab
2024-07-20 18:16 ` |PENDING| " dpdklab
2024-07-20 18:20 ` |FAILURE| " dpdklab
2024-07-20 18:21 ` |PENDING| " dpdklab
2024-07-20 18:21 ` |FAILURE| " dpdklab
2024-07-20 18:22 ` |PENDING| " dpdklab
2024-07-20 18:23 ` dpdklab
2024-07-20 18:24 ` |FAILURE| " dpdklab
2024-07-20 18:24 ` dpdklab
2024-07-20 18:27 ` |PENDING| " dpdklab
2024-07-20 18:29 ` dpdklab
2024-07-20 18:29 ` |FAILURE| " dpdklab
2024-07-20 18:32 ` dpdklab
2024-07-20 18:32 ` dpdklab
2024-07-20 18:33 ` dpdklab
2024-07-20 18:34 ` |PENDING| " dpdklab
2024-07-20 18:35 ` dpdklab
2024-07-20 18:35 ` dpdklab
2024-07-20 18:35 ` |SUCCESS| " dpdklab
2024-07-20 18:38 ` |PENDING| " dpdklab
2024-07-20 18:40 ` |SUCCESS| " dpdklab
2024-07-20 18:41 ` dpdklab
2024-07-20 19:07 ` |FAILURE| " dpdklab
2024-07-20 19:15 ` dpdklab
2024-07-20 19:24 ` 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=669bfab9.050a0220.2d501.2a41SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=Sivaprasad.Tummala@amd.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).