automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: anoobj@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw139444 [PATCH v2 7/7] dma/odm: add remaining ops
Date: Wed, 17 Apr 2024 04:44:33 -0400	[thread overview]
Message-ID: <20240417084433.333817-1-robot@bytheb.org> (raw)
In-Reply-To: <20240417072708.322-8-anoobj@marvell.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
                cmpl.u = rte_atomic_load_explicit(cmpl_ptr, rte_memory_order_relaxed);
                         ^                        ~~~~~~~~
../lib/eal/include/rte_stdatomic.h:73:2: note: expanded from macro 'rte_atomic_load_explicit'
        atomic_load_explicit(ptr, memorder)
        ^                    ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:130:30: note: expanded from macro 'atomic_load_explicit'
#define atomic_load_explicit __c11_atomic_load
                             ^
../drivers/dma/odm/odm_dmadev.c:518:3: error: address argument to atomic operation must be a pointer to _Atomic type ('uint32_t *' (aka 'unsigned int *') invalid)
                rte_atomic_store_explicit(cmpl_ptr, cmpl_zero.u, rte_memory_order_relaxed);
                ^                         ~~~~~~~~
../lib/eal/include/rte_stdatomic.h:76:2: note: expanded from macro 'rte_atomic_store_explicit'
        atomic_store_explicit(ptr, val, memorder)
        ^                     ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:127:31: note: expanded from macro 'atomic_store_explicit'
#define atomic_store_explicit __c11_atomic_store
                              ^
4 errors generated.
[1068/2962] Compiling C object 'drivers/a715181@@rte_dma_idxd@sha/meson-generated_.._rte_dma_idxd.pmd.c.o'.
[1069/2962] Compiling C object 'drivers/a715181@@rte_dma_dpaa2@sta/meson-generated_.._rte_dma_dpaa2.pmd.c.o'.
[1070/2962] Linking static target drivers/libtmp_rte_dma_ioat.a.
[1071/2962] Compiling C object 'drivers/a715181@@tmp_rte_dma_odm@sta/dma_odm_odm.c.o'.
[1072/2962] Generating rte_common_sfc_efx.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-clang-stdatomic" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-04-17  8:44 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417072708.322-8-anoobj@marvell.com>
2024-04-17  7:11 ` |SUCCESS| pw139438-139444 " qemudev
2024-04-17  7:15 ` qemudev
2024-04-17  7:29 ` |WARNING| pw139444 " checkpatch
2024-04-17  8:44 ` 0-day Robot [this message]
2024-04-17  9:51 ` |SUCCESS| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op dpdklab
2024-04-17  9:52 ` dpdklab
2024-04-17  9:53 ` dpdklab
2024-04-17  9:54 ` dpdklab
2024-04-17  9:55 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:21 ` dpdklab
2024-04-17 10:23 ` dpdklab
2024-04-17 10:25 ` dpdklab
2024-04-17 10:26 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:28 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:43 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:51 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:20 ` dpdklab
2024-04-17 11:24 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:43 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:49 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 12:00 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` 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=20240417084433.333817-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=anoobj@marvell.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).