From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mattias.ronnblom@ericsson.com, robot@bytheb.org
Subject: |FAILURE| pw146035 [RFC v2 10/10] eventdev: remove single event enqueue and dequeue
Date: Tue, 15 Oct 2024 15:22:44 -0400 [thread overview]
Message-ID: <20241015192244.1060163-1-robot@bytheb.org> (raw)
In-Reply-To: <20241015182535.825098-11-mattias.ronnblom@ericsson.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/146035/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11352424751
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-shared-aarch64" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-shared-aarch64" at step Build and test
####################################################################################
| ^~~~~~
../drivers/event/cnxk/cn9k_eventdev.c: In function ‘cn9k_sso_fp_fns_set’:
../drivers/event/cnxk/cn9k_eventdev.c:576:20: error: ‘struct rte_eventdev’ has no member named ‘enqueue’; did you mean ‘ca_enqueue’?
576 | event_dev->enqueue = cn9k_sso_hws_enq;
| ^~~~~~~
| ca_enqueue
../drivers/event/cnxk/cn9k_eventdev.c:576:30: error: ‘cn9k_sso_hws_enq’ undeclared (first use in this function); did you mean ‘cn9k_sso_hws_link’?
576 | event_dev->enqueue = cn9k_sso_hws_enq;
| ^~~~~~~~~~~~~~~~
| cn9k_sso_hws_link
../drivers/event/cnxk/cn9k_eventdev.c:584:28: error: ‘struct rte_eventdev’ has no member named ‘enqueue’; did you mean ‘ca_enqueue’?
584 | event_dev->enqueue = cn9k_sso_hws_dual_enq;
| ^~~~~~~
| ca_enqueue
../drivers/event/cnxk/cn9k_eventdev.c:584:38: error: ‘cn9k_sso_hws_dual_enq’ undeclared (first use in this function); did you mean ‘cn9k_sso_hws_dual_ca_enq’?
584 | event_dev->enqueue = cn9k_sso_hws_dual_enq;
| ^~~~~~~~~~~~~~~~~~~~~
| cn9k_sso_hws_dual_ca_enq
[2451/4290] Compiling C object 'drivers/a715181@@tmp_rte_event_cnxk@sta/event_cnxk_deq_cn9k_deq_64_79_seg_burst.c.o'.
[2452/4290] Compiling C object 'drivers/a715181@@tmp_rte_event_cnxk@sta/event_cnxk_deq_cn9k_deq_80_95_seg_burst.c.o'.
[2453/4290] Generating rte_crypto_octeontx.sym_chk with a meson_exe.py custom command.
[2454/4290] Compiling C object 'drivers/a715181@@tmp_rte_event_cnxk@sta/event_cnxk_deq_cn9k_deq_96_111_seg_burst.c.o'.
[2455/4290] Compiling C object 'drivers/a715181@@tmp_rte_event_cnxk@sta/event_cnxk_deq_cn9k_deq_112_127_seg_burst.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-shared-aarch64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-10-15 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241015182535.825098-11-mattias.ronnblom@ericsson.com>
2024-10-15 18:09 ` |SUCCESS| pw146037-146035 " qemudev
2024-10-15 18:14 ` qemudev
2024-10-15 18:36 ` |WARNING| pw146035 " checkpatch
2024-10-15 19:22 ` 0-day Robot [this message]
2024-10-15 21:54 ` |SUCCESS| pw146037-146035 [PATCH] [RFC,v2,10/10] eventdev: remove si dpdklab
2024-10-15 21:58 ` dpdklab
2024-10-15 22:16 ` dpdklab
2024-10-16 7:29 ` dpdklab
2024-10-16 9:39 ` dpdklab
2024-10-16 18:08 ` |PENDING| " dpdklab
2024-10-16 18:26 ` |SUCCESS| " dpdklab
2024-10-16 18:27 ` |PENDING| " dpdklab
2024-10-16 18:42 ` dpdklab
2024-10-16 19:14 ` |SUCCESS| " dpdklab
2024-10-16 19:58 ` dpdklab
2024-10-16 21:55 ` |FAILURE| " dpdklab
2024-10-17 0:35 ` |WARNING| " dpdklab
2024-10-17 3:08 ` dpdklab
2024-10-19 5:57 ` |SUCCESS| " 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=20241015192244.1060163-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=mattias.ronnblom@ericsson.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).