From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: g.singh@nxp.com, robot@bytheb.org
Subject: |FAILURE| pw153885 [PATCH 11/11] net/dpaa2: enable software taildrop for ordered queues
Date: Fri, 30 May 2025 04:24:31 -0400 [thread overview]
Message-ID: <20250530082431.796440-1-robot@bytheb.org> (raw)
In-Reply-To: <20250530071344.2939434-12-g.singh@nxp.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153885/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15341570701
Build Logs:
-----------------------Summary of failed steps-----------------------
"Check patches" failed at step Check patches
"ubuntu-22.04-gcc-static-i386" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "Check patches" at step Check patches
####################################################################################
^[[36;1mdevtools/check-doc-vs-code.sh upstream/main || failed=true^[[0m
^[[36;1mdevtools/check-meson.py || failed=true^[[0m
^[[36;1mdevtools/check-spdx-tag.sh || failed=true^[[0m
^[[36;1m[ -z "$failed" ]^[[0m
shell: /usr/bin/bash --noprofile --norc -exo pipefail {0}
env:
REF_GIT_BRANCH: main
REF_GIT_REPO: https://github.com/DPDK/dpdk
REF_GIT_TAG: v25.03
##[endgroup]
+ git remote add upstream https://github.com/DPDK/dpdk
+ git fetch upstream main
From https://github.com/DPDK/dpdk
* branch main -> FETCH_HEAD
* [new branch] main -> upstream/main
+ failed=
+ devtools/check-doc-vs-code.sh upstream/main
+ devtools/check-meson.py
+ devtools/check-spdx-tag.sh
drivers/net/dpaa2/mc/fsl_dpmac.h
drivers/net/dpaa2/mc/fsl_dpmac.h
total: 1 missing SPDX, 0 license errors, 1 warnings
+ failed=true
+ '[' -z true ']'
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "Check patches" at step Check patches
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-i386" at step Build and test
####################################################################################
| |
| size_t * {aka unsigned int *}
In file included from ../drivers/bus/fslmc/portal/dpaa2_hw_pvt.h:16,
from ../drivers/mempool/dpaa2/dpaa2_hw_mempool.c:30:
../drivers/bus/fslmc/qbman/include/fsl_qbman_portal.h:1217:69: note: expected ‘uint64_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘size_t *’ {aka ‘unsigned int *’}
1217 | int qbman_swp_acquire(struct qbman_swp *s, uint16_t bpid, uint64_t *buffers,
| ~~~~~~~~~~^~~~~~~
../drivers/mempool/dpaa2/dpaa2_hw_mempool.c:460:52: error: passing argument 3 of ‘qbman_swp_acquire’ from incompatible pointer type [-Werror=incompatible-pointer-types]
460 | ret = qbman_swp_acquire(swp, bpid, bufs,
| ^~~~
| |
| size_t * {aka unsigned int *}
In file included from ../drivers/bus/fslmc/portal/dpaa2_hw_pvt.h:16,
from ../drivers/mempool/dpaa2/dpaa2_hw_mempool.c:30:
../drivers/bus/fslmc/qbman/include/fsl_qbman_portal.h:1217:69: note: expected ‘uint64_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘size_t *’ {aka ‘unsigned int *’}
1217 | int qbman_swp_acquire(struct qbman_swp *s, uint16_t bpid, uint64_t *buffers,
| ~~~~~~~~~~^~~~~~~
cc1: all warnings being treated as errors
[277/5846] Compiling C object drivers/libtmp_rte_mempool_dpaa.a.p/mempool_dpaa_dpaa_mempool.c.o
[278/5846] Compiling C object lib/librte_acl.a.p/acl_acl_run_scalar.c.o
[279/5846] Compiling C object lib/librte_acl.a.p/acl_acl_bld.c.o
[280/5846] Compiling C object lib/librte_acl.a.p/acl_acl_gen.c.o
[281/5846] Compiling C object lib/librte_acl_avx2_lib.a.p/acl_acl_run_avx2.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-i386" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-05-30 8:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250530071344.2939434-12-g.singh@nxp.com>
2025-05-30 6:41 ` |SUCCESS| pw153875-153885 " qemudev
2025-05-30 6:46 ` qemudev
2025-05-30 7:15 ` |SUCCESS| pw153885 " checkpatch
2025-05-30 8:24 ` 0-day Robot [this message]
2025-05-30 9:46 ` |SUCCESS| pw153875-153885 [PATCH] [11/11] net/dpaa2: enable software dpdklab
2025-05-30 10:15 ` dpdklab
2025-05-30 10:19 ` dpdklab
2025-05-30 10:20 ` dpdklab
2025-05-30 10:21 ` dpdklab
2025-05-30 10:41 ` dpdklab
2025-05-30 11:35 ` |PENDING| " dpdklab
2025-05-30 11:56 ` dpdklab
2025-05-30 12:54 ` |FAILURE| " dpdklab
2025-05-30 12:56 ` |SUCCESS| " dpdklab
2025-05-30 13:21 ` |FAILURE| " dpdklab
2025-05-30 13:33 ` dpdklab
2025-05-30 14:36 ` dpdklab
2025-05-30 20:53 ` dpdklab
2025-05-30 21:08 ` |SUCCESS| " dpdklab
2025-05-30 23:43 ` |FAILURE| " dpdklab
2025-05-30 23:47 ` dpdklab
2025-05-31 8:43 ` |SUCCESS| " dpdklab
2025-05-31 8:59 ` dpdklab
2025-05-31 9:57 ` dpdklab
2025-06-04 16: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=20250530082431.796440-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=g.singh@nxp.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).