automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: daniel.gregory@bytedance.com, robot@bytheb.org
Subject: |FAILURE| pw140506 [PATCH 2/2] eal/riscv: add support for zicbop extension
Date: Thu, 30 May 2024 14:24:01 -0400	[thread overview]
Message-ID: <20240530182401.2224156-1-robot@bytheb.org> (raw)
In-Reply-To: <20240530171948.19763-3-daniel.gregory@bytedance.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/140506/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9306912337
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-riscv64" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-riscv64" at step Build and test
####################################################################################
In file included from ../lib/mbuf/rte_mbuf.h:39,
                 from ../lib/net/rte_ether.h:22,
                 from ../lib/net/rte_arp.h:15,
                 from ../lib/net/rte_arp.c:5:
../lib/eal/riscv/include/rte_prefetch.h: In function ‘rte_prefetch0’:
../lib/eal/riscv/include/rte_prefetch.h:34:28: error: cast discards ‘volatile’ qualifier from pointer target type [-Werror=cast-qual]
   34 |         __builtin_prefetch((const void *)p);
      |                            ^
cc1: all warnings being treated as errors
[97/3440] Linking static target lib/librte_mempool.a.
[98/3440] Compiling C object 'lib/76b5a35@@rte_mbuf@sta/mbuf_rte_mbuf.c.o'.
FAILED: lib/76b5a35@@rte_mbuf@sta/mbuf_rte_mbuf.c.o 
ccache riscv64-linux-gnu-gcc -Ilib/76b5a35@@rte_mbuf@sta -Ilib -I../lib -Ilib/mbuf -I../lib/mbuf -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/riscv/include -I../lib/eal/riscv/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -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-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=rv64gc -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.mbuf -MD -MQ 'lib/76b5a35@@rte_mbuf@sta/mbuf_rte_mbuf.c.o' -MF 'lib/76b5a35@@rte_mbuf@sta/mbuf_rte_mbuf.c.o.d' -o 'lib/76b5a35@@rte_mbuf@sta/mbuf_rte_mbuf.c.o' -c ../lib/mbuf/rte_mbuf.c
In file included from ../lib/mbuf/rte_mbuf.h:39,
                 from ../lib/mbuf/rte_mbuf.c:17:
../lib/eal/riscv/include/rte_prefetch.h: In function ‘rte_prefetch0’:
../lib/eal/riscv/include/rte_prefetch.h:34:28: error: cast discards ‘volatile’ qualifier from pointer target type [-Werror=cast-qual]
   34 |         __builtin_prefetch((const void *)p);
      |                            ^
cc1: all warnings being treated as errors
[99/3440] Compiling C object 'lib/76b5a35@@rte_rcu@sta/rcu_rte_rcu_qsbr.c.o'.
[100/3440] Generating ring.sym_chk with a meson_exe.py custom command.
[101/3440] Generating eal.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-riscv64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-05-30 18:24 UTC|newest]

Thread overview: 184+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240530171948.19763-3-daniel.gregory@bytedance.com>
2024-05-30 16:54 ` |SUCCESS| pw140505-140506 " qemudev
2024-05-30 16:59 ` qemudev
2024-05-30 17:21 ` |SUCCESS| pw140506 " checkpatch
2024-05-30 18:13 ` |SUCCESS| pw140505-140506 [PATCH] [2/2] eal/riscv: add support for z dpdklab
2024-05-30 18:15 ` dpdklab
2024-05-30 18:24 ` 0-day Robot [this message]
2024-05-30 18:42 ` dpdklab
2024-05-30 18:46 ` dpdklab
2024-05-30 18:46 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:47 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:48 ` dpdklab
2024-05-30 18:49 ` dpdklab
2024-05-30 18:50 ` dpdklab
2024-05-30 18:50 ` dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 18:52 ` dpdklab
2024-05-30 18:53 ` dpdklab
2024-05-30 18:53 ` dpdklab
2024-05-30 18:55 ` dpdklab
2024-05-30 19:11 ` dpdklab
2024-05-30 19:11 ` dpdklab
2024-05-30 19:12 ` dpdklab
2024-05-30 19:13 ` dpdklab
2024-05-30 19:14 ` dpdklab
2024-05-30 19:14 ` dpdklab
2024-05-30 19:15 ` dpdklab
2024-05-30 19:15 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:17 ` dpdklab
2024-05-30 19:19 ` dpdklab
2024-05-30 19:20 ` dpdklab
2024-05-30 19:21 ` dpdklab
2024-05-30 19:23 ` dpdklab
2024-05-30 19:24 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:26 ` dpdklab
2024-05-30 19:27 ` dpdklab
2024-05-30 19:27 ` dpdklab
2024-05-30 19:28 ` dpdklab
2024-05-30 19:28 ` dpdklab
2024-05-30 19:29 ` dpdklab
2024-05-30 19:31 ` dpdklab
2024-05-30 19:32 ` dpdklab
2024-05-30 19:32 ` dpdklab
2024-05-30 19:33 ` dpdklab
2024-05-30 19:36 ` dpdklab
2024-05-30 19:36 ` dpdklab
2024-05-30 19:41 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:44 ` dpdklab
2024-05-30 19:44 ` dpdklab
2024-05-30 19:45 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:46 ` dpdklab
2024-05-30 19:48 ` dpdklab
2024-05-30 19:48 ` dpdklab
2024-05-30 19:49 ` dpdklab
2024-05-30 19:53 ` dpdklab
2024-05-30 19:53 ` dpdklab
2024-05-30 20:33 ` dpdklab
2024-05-30 20:36 ` dpdklab
2024-05-30 20:37 ` dpdklab
2024-05-30 20:37 ` dpdklab
2024-05-30 20:38 ` dpdklab
2024-05-30 20:43 ` dpdklab
2024-05-30 20:45 ` dpdklab
2024-05-30 20:47 ` dpdklab
2024-05-30 20:52 ` dpdklab
2024-05-30 20:53 ` dpdklab
2024-05-30 21:02 ` dpdklab
2024-05-30 21:48 ` dpdklab
2024-05-30 22:35 ` dpdklab
2024-05-30 22:50 ` dpdklab
2024-05-30 23:00 ` dpdklab
2024-05-30 23:13 ` dpdklab
2024-05-30 23:13 ` dpdklab
2024-06-01  1:41 ` dpdklab
2024-06-01  1:44 ` dpdklab
2024-06-01  1:45 ` dpdklab
2024-06-01  1:46 ` dpdklab
2024-06-01  1:48 ` dpdklab
2024-06-01  1:49 ` dpdklab
2024-06-01  1:49 ` dpdklab
2024-06-01  1:50 ` dpdklab
2024-06-01  2:07 ` dpdklab
2024-06-01  2:53 ` dpdklab
2024-06-01  3:00 ` dpdklab
2024-06-01  3:01 ` dpdklab
2024-06-01  3:01 ` dpdklab
2024-06-01  3:02 ` dpdklab
2024-06-01  3:04 ` dpdklab
2024-06-01  3:07 ` dpdklab
2024-06-01  3:16 ` dpdklab
2024-06-01  3:17 ` dpdklab
2024-06-01  3:18 ` dpdklab
2024-06-01  3:20 ` dpdklab
2024-06-01  3:20 ` dpdklab
2024-06-01  3:32 ` dpdklab
2024-06-01  3:33 ` dpdklab
2024-06-01  3:36 ` dpdklab
2024-06-01  3:46 ` dpdklab
2024-06-01  3:47 ` dpdklab
2024-06-01  3:47 ` dpdklab
2024-06-01  3:52 ` dpdklab
2024-06-01  3:52 ` dpdklab
2024-06-01  3:54 ` dpdklab
2024-06-01  3:55 ` dpdklab
2024-06-01  3:55 ` dpdklab
2024-06-01  3:56 ` dpdklab
2024-06-01  3:56 ` dpdklab
2024-06-01  3:57 ` dpdklab
2024-06-01  3:57 ` dpdklab
2024-06-01  4:03 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:04 ` dpdklab
2024-06-01  4:05 ` dpdklab
2024-06-01  4:05 ` dpdklab
2024-06-01  4:06 ` dpdklab
2024-06-01  4:06 ` dpdklab
2024-06-01  4:07 ` dpdklab
2024-06-01  4:07 ` dpdklab
2024-06-01  4:08 ` dpdklab
2024-06-01  4:08 ` dpdklab
2024-06-01  4:14 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:15 ` dpdklab
2024-06-01  4:16 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:17 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:18 ` dpdklab
2024-06-01  4:21 ` dpdklab
2024-06-01  4:21 ` dpdklab
2024-06-01  4:22 ` dpdklab
2024-06-01  4:23 ` dpdklab
2024-06-01  4:27 ` dpdklab
2024-06-01  4:42 ` dpdklab
2024-06-01  4:46 ` dpdklab
2024-06-01  4:47 ` dpdklab
2024-06-01  4:48 ` dpdklab
2024-06-01  4:50 ` dpdklab
2024-06-01  4:51 ` dpdklab
2024-06-01  4:55 ` dpdklab
2024-06-01  4:56 ` dpdklab
2024-06-01  4:56 ` dpdklab
2024-06-01  5:19 ` dpdklab
2024-06-01  5:20 ` dpdklab
2024-06-01  5:21 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:22 ` dpdklab
2024-06-01  5:53 ` dpdklab
2024-06-01  6:00 ` dpdklab
2024-06-01  6:09 ` dpdklab
2024-06-01  6:09 ` dpdklab
2024-06-01  6:10 ` dpdklab
2024-06-01  6:21 ` dpdklab
2024-06-01  6:46 ` dpdklab
2024-06-01  6:57 ` dpdklab
2024-06-01  7:03 ` dpdklab
2024-06-01  7:26 ` dpdklab
2024-06-01 11:55 ` |FAILURE| " dpdklab
2024-06-01 13:36 ` dpdklab
2024-06-01 20:33 ` |SUCCESS| " dpdklab
2024-06-24 17:33 ` |PENDING| " 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=20240530182401.2224156-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=daniel.gregory@bytedance.com \
    --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).