automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: christian.ehrhardt@canonical.com, zhoumin@loongson.cn
Subject: |FAILURE| pw134588 [PATCH 1/1] eal/linux: force iova-mode va without pa available
Date: Thu, 23 Nov 2023 23:31:32 +0800	[thread overview]
Message-ID: <202311231531.3ANFVWvh142266@localhost.localdomain> (raw)
In-Reply-To: <20231123155149.306556-2-christian.ehrhardt@canonical.com>

Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/134588

_ninja build failure_

Submitter: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thu, 23 Nov 2023 16:51:49 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 0e9dd79c90e907bcf69851434882f7877cdc3dd8

134588 --> ninja build failed

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: lib/librte_eal.a.p/eal_linux_eal.c.o
cc -Ilib/librte_eal.a.p -Ilib -I../lib -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/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 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation '-DABI_VERSION="24.0"' -DRTE_LOG_DEFAULT_LOGTYPE=lib.eal -MD -MQ lib/librte_eal.a.p/eal_
 linux_eal.c.o -MF lib/librte_eal.a.p/eal_linux_eal.c.o.d -o lib/librte_eal.a.p/eal_linux_eal.c.o -c ../lib/eal/linux/eal.c
./lib/eal/linux/eal.c: In function ‘rte_eal_init’:
./lib/eal/linux/eal.c:1074:3: error: ‘iova_mode’ undeclared (first use in this function); did you mean ‘rte_iova_mode’?
iova_mode = RTE_IOVA_VA;
^~~~~~~~~
rte_iova_mode
./lib/eal/linux/eal.c:1074:3: note: each undeclared identifier is reported only once for each function it appears in
[45/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_thread.c.o
[46/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_trace_utils.c.o
[47/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_dynmem.c.o
[48/2420] Compiling C object lib/librte_eal.a.p/eal_loongarch_rte_hypervisor.c.o
[49/2420] Compiling C object lib/librte_eal.a.p/eal_loongarch_rte_cpuflags.c.o
[50/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_lcore.c.o
[51/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_timer.c.o
[52/2420] Compiling C object lib/librte_eal.a.p/eal_loongarch_rte_cycles.c.o
[53/2420] Compiling C object lib/librte_eal.a.p/eal_loongarch_rte_power_intrinsics.c.o
[54/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_lcore.c.o
[55/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_vfio_mp_sync.c.o
[56/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_trace.c.o
[57/2420] Compiling C object lib/librte_eal.a.p/eal_common_rte_malloc.c.o
[58/2420] Compiling C object lib/librte_eal.a.p/eal_unix_rte_thread.c.o
[59/2420] Compiling C object lib/librte_eal.a.p/eal_common_malloc_mp.c.o
[60/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_alarm.c.o
[61/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_dev.c.o
[62/2420] Compiling C object lib/librte_ring.a.p/ring_rte_ring.c.o
[63/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_hugepage_info.c.o
[64/2420] Compiling C object lib/librte_eal.a.p/eal_common_malloc_heap.c.o
[65/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_proc.c.o
[66/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_fbarray.c.o
[67/2420] Compiling C object lib/librte_eal.a.p/eal_common_rte_service.c.o
[68/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_memory.c.o
[69/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_interrupts.c.o
[70/2420] Compiling C object lib/librte_telemetry.a.p/telemetry_telemetry.c.o
[71/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_memalloc.c.o
[72/2420] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_options.c.o
[73/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_memory.c.o
[74/2420] Compiling C object lib/librte_eal.a.p/eal_linux_eal_vfio.c.o
[75/2420] Generating kvargs.sym_chk with a custom command (wrapped by meson to capture output)
[76/2420] Compiling C object lib/librte_rcu.a.p/rcu_rte_rcu_qsbr.c.o
[77/2420] Generating log.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


       reply	other threads:[~2023-11-23 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231123155149.306556-2-christian.ehrhardt@canonical.com>
2023-11-23 15:31 ` qemudev [this message]
2023-11-23 15:53 ` |WARNING| " checkpatch
2023-11-23 16:19 ` |FAILURE| " 0-day Robot
2023-11-23 17:21 |FAILURE| pw134588 [PATCH] [1/1] " 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=202311231531.3ANFVWvh142266@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=christian.ehrhardt@canonical.com \
    --cc=test-report@dpdk.org \
    --cc=zhoumin@loongson.cn \
    /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).