automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wang.junlong1@zte.com.cn, robot@bytheb.org
Subject: |FAILURE| pw143816 [PATCH v3] net/zxdh: Provided zxdh basic init
Date: Mon,  9 Sep 2024 08:25:17 -0400	[thread overview]
Message-ID: <20240909122517.1808826-1-robot@bytheb.org> (raw)
In-Reply-To: <20240909113140.3805558-1-wang.junlong1@zte.com.cn>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10772518247
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/net/zxdh/zxdh_msg.c:845:32: note: include ‘<stdlib.h>’ or provide a declaration of ‘malloc’
../drivers/net/zxdh/zxdh_msg.c:859:9: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration]
  859 |         free(reps_buffer);
      |         ^~~~
../drivers/net/zxdh/zxdh_msg.c:859:9: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’
../drivers/net/zxdh/zxdh_msg.c:859:9: error: incompatible implicit declaration of built-in function ‘free’ [-Werror=builtin-declaration-mismatch]
../drivers/net/zxdh/zxdh_msg.c:859:9: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’
../drivers/net/zxdh/zxdh_msg.c: In function ‘zxdh_bar_irq_recv’:
../drivers/net/zxdh/zxdh_msg.c:903:31: error: incompatible implicit declaration of built-in function ‘malloc’ [-Werror=builtin-declaration-mismatch]
  903 |         uint8_t *recved_msg = malloc(msg_header.len);
      |                               ^~~~~~
../drivers/net/zxdh/zxdh_msg.c:903:31: note: include ‘<stdlib.h>’ or provide a declaration of ‘malloc’
../drivers/net/zxdh/zxdh_msg.c:924:9: error: incompatible implicit declaration of built-in function ‘free’ [-Werror=builtin-declaration-mismatch]
  924 |         free(recved_msg);
      |         ^~~~
../drivers/net/zxdh/zxdh_msg.c:924:9: note: include ‘<stdlib.h>’ or provide a declaration of ‘free’
cc1: all warnings being treated as errors
[2089/4226] Compiling C object 'drivers/a715181@@tmp_rte_net_virtio@sta/net_virtio_virtio_user_virtio_user_dev.c.o'.
[2090/4226] Compiling C object 'drivers/a715181@@tmp_rte_net_zxdh@sta/net_zxdh_zxdh_npsdk.c.o'.
[2091/4226] Compiling C object 'drivers/a715181@@tmp_rte_net_zxdh@sta/net_zxdh_zxdh_queue.c.o'.
[2092/4226] Compiling C object 'drivers/a715181@@tmp_rte_net_vmxnet3@sta/net_vmxnet3_vmxnet3_ethdev.c.o'.
[2093/4226] Compiling C object 'drivers/a715181@@tmp_rte_net_zxdh@sta/net_zxdh_zxdh_ethdev.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-----------------------------

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

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240909113140.3805558-1-wang.junlong1@zte.com.cn>
2024-09-09 11:19 ` |SUCCESS| " qemudev
2024-09-09 11:23 ` qemudev
2024-09-09 11:33 ` |WARNING| " checkpatch
2024-09-09 12:25 ` 0-day Robot [this message]
2024-09-09 14:31 ` |PENDING| pw143816 [PATCH] [v3] " dpdklab
2024-09-09 14:38 ` |SUCCESS| " dpdklab
2024-09-09 14:39 ` dpdklab
2024-09-09 14:42 ` dpdklab
2024-09-09 14:47 ` |PENDING| " dpdklab
2024-09-09 14:54 ` |SUCCESS| " dpdklab
2024-09-09 15:08 ` dpdklab
2024-09-09 15:15 ` |FAILURE| " dpdklab
2024-09-09 15:15 ` dpdklab
2024-09-09 15:19 ` dpdklab
2024-09-09 15:21 ` dpdklab
2024-09-09 15:23 ` dpdklab
2024-09-09 15:25 ` dpdklab
2024-09-09 15:25 ` |PENDING| " dpdklab
2024-09-09 15:28 ` |FAILURE| " dpdklab
2024-09-09 15:29 ` dpdklab
2024-09-09 15:30 ` dpdklab
2024-09-09 15:31 ` dpdklab
2024-09-09 15:33 ` |WARNING| " dpdklab
2024-09-09 15:34 ` |FAILURE| " dpdklab
2024-09-09 15:37 ` |SUCCESS| " dpdklab
2024-09-09 15:41 ` |FAILURE| " dpdklab
2024-09-09 15:41 ` dpdklab
2024-09-09 15:43 ` dpdklab
2024-09-09 15:46 ` dpdklab
2024-09-09 15:48 ` dpdklab
2024-09-09 15:48 ` dpdklab
2024-09-09 15:49 ` dpdklab
2024-09-09 15:50 ` dpdklab
2024-09-09 15:55 ` dpdklab
2024-09-09 16:05 ` |SUCCESS| " dpdklab
2024-09-09 16:06 ` |FAILURE| " dpdklab
2024-09-09 16:11 ` |SUCCESS| " dpdklab
2024-09-09 16:12 ` |FAILURE| " dpdklab
2024-09-09 16:12 ` |WARNING| " dpdklab
2024-09-09 16:12 ` |FAILURE| " dpdklab
2024-09-09 16:13 ` dpdklab
2024-09-09 16:15 ` |SUCCESS| " dpdklab
2024-09-09 16:34 ` |FAILURE| " dpdklab
2024-09-09 16:35 ` |SUCCESS| " dpdklab
2024-09-09 17:10 ` dpdklab
2024-09-09 17:11 ` dpdklab
2024-09-09 17:20 ` dpdklab
2024-09-09 18:20 ` dpdklab
2024-09-09 18:58 ` dpdklab
2024-09-16 11:33 ` dpdklab
2024-09-16 21:37 ` 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=20240909122517.1808826-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=test-report@dpdk.org \
    --cc=wang.junlong1@zte.com.cn \
    /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).