automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: gmuthukrishn@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw149466 [v1 16/16] test/crypto: test virtio_crypto_user PMD
Date: Tue, 24 Dec 2024 03:25:43 -0500	[thread overview]
Message-ID: <20241224082543.3961185-1-robot@bytheb.org> (raw)
In-Reply-To: <854b1ec12217bda2cd624431f95ab771114aaaa7.1735025264.git.gmuthukrishn@marvell.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1435:24: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1446:23: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->cipher.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RW);
                                           ^
../lib/vhost/vhost_crypto.c:1455:23: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->cipher.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                           ^
../lib/vhost/vhost_crypto.c:1458:24: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1474:18: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
        vc_req->inhdr = get_data_ptr(vc_req, desc, VHOST_ACCESS_WO);
                        ^
9 errors generated.
[423/3221] Generating symbol file lib/librte_mldev.so.25.1.p/librte_mldev.so.25.1.symbols
[424/3221] Compiling C object lib/librte_ipsec.a.p/ipsec_esp_inb.c.o
[425/3221] Compiling C object lib/librte_vhost.a.p/vhost_vhost_user.c.o
[426/3221] Compiling C object lib/librte_vhost.a.p/vhost_vhost.c.o
[427/3221] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
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
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1435:24: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1446:23: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->cipher.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RW);
                                           ^
../lib/vhost/vhost_crypto.c:1455:23: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->cipher.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                           ^
../lib/vhost/vhost_crypto.c:1458:24: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                        rsa->message.data = get_data_ptr(vc_req, desc, VHOST_ACCESS_RO);
                                            ^
../lib/vhost/vhost_crypto.c:1474:18: error: calling function 'get_data_ptr' requires holding mutex 'vc_req->vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
        vc_req->inhdr = get_data_ptr(vc_req, desc, VHOST_ACCESS_WO);
                        ^
9 errors generated.
[434/6645] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net_ctrl.c.o
[435/6645] Compiling C object lib/librte_vhost.a.p/vhost_vhost.c.o
[436/6645] Compiling C object lib/librte_vhost.a.p/vhost_vhost_user.c.o
[437/6645] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
[438/6645] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "fedora:39-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-12-24  8:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <854b1ec12217bda2cd624431f95ab771114aaaa7.1735025264.git.gmuthukrishn@marvell.com>
2024-12-24  7:09 ` |SUCCESS| pw149451-149466 " qemudev
2024-12-24  7:14 ` qemudev
2024-12-24  7:40 ` |SUCCESS| pw149466 " checkpatch
2024-12-24  8:25 ` 0-day Robot [this message]
2024-12-24  9:20 ` |SUCCESS| pw149451-149466 [PATCH] [v1,16/16] test/crypto: test virti dpdklab
2024-12-24  9:22 ` dpdklab
2024-12-24  9:22 ` dpdklab
2024-12-24  9:23 ` dpdklab
2024-12-24  9:24 ` |FAILURE| " dpdklab
2024-12-24  9:28 ` dpdklab
2024-12-24  9:29 ` dpdklab
2024-12-24  9:32 ` |SUCCESS| " dpdklab
2024-12-24  9:32 ` dpdklab
2024-12-24  9:45 ` |WARNING| " dpdklab
2024-12-24  9:48 ` |SUCCESS| " dpdklab
2024-12-24  9:59 ` |PENDING| " dpdklab
2024-12-24 10:00 ` |SUCCESS| " dpdklab
2024-12-24 10:03 ` |FAILURE| " dpdklab
2024-12-24 10:18 ` |WARNING| " dpdklab
2024-12-24 10:35 ` |SUCCESS| " dpdklab
2024-12-24 10:40 ` |FAILURE| " dpdklab
2024-12-24 11:12 ` |WARNING| " dpdklab
2024-12-24 14:15 ` |FAILURE| " 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=20241224082543.3961185-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=gmuthukrishn@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).