From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: yidingx.zhou@intel.com, robot@bytheb.org
Subject: |FAILURE| pw116416 [PATCH v2] net/iavf: fix error of virtchnl command
Date: Mon, 19 Sep 2022 04:59:56 -0400 [thread overview]
Message-ID: <20220919085956.3994388-1-robot@bytheb.org> (raw)
In-Reply-To: <20220919075358.1299338-1-yidingx.zhou@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/116416/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/3080802837
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-static-mingw" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-static-mingw" at step Build and test
####################################################################################
../drivers/net/iavf/iavf_vchnl.c:124:36: error: ‘F_GETFL’ undeclared (first use in this function)
124 | int flags = fcntl(handler->fd[1], F_GETFL);
| ^~~~~~~
../drivers/net/iavf/iavf_vchnl.c:124:36: note: each undeclared identifier is reported only once for each function it appears in
../drivers/net/iavf/iavf_vchnl.c:125:24: error: ‘F_SETFL’ undeclared (first use in this function)
125 | fcntl(handler->fd[1], F_SETFL, flags | O_NONBLOCK);
| ^~~~~~~
../drivers/net/iavf/iavf_vchnl.c:125:41: error: ‘O_NONBLOCK’ undeclared (first use in this function)
125 | fcntl(handler->fd[1], F_SETFL, flags | O_NONBLOCK);
| ^~~~~~~~~~
In file included from ../lib/eal/include/rte_per_lcore.h:25,
from ../lib/eal/include/rte_eal.h:19,
from ../drivers/net/iavf/iavf_vchnl.c:20:
../drivers/net/iavf/iavf_vchnl.c: In function ‘iavf_dev_event_handler_fini’:
../lib/eal/windows/include/pthread.h:43:32: error: value computed is not used [-Werror=unused-value]
43 | #define pthread_cancel(thread) !TerminateThread((HANDLE) thread, 0)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/iavf/iavf_vchnl.c:143:2: note: in expansion of macro ‘pthread_cancel’
143 | pthread_cancel(handler->tid);
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[421/1305] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_rxtx.c.obj'.
[422/1305] Compiling C object 'drivers/net/iavf/cd88e11@@iavf_avx512_lib@sta/iavf_rxtx_vec_avx512.c.obj'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2022-09-19 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220919075358.1299338-1-yidingx.zhou@intel.com>
2022-09-19 7:52 ` |WARNING| " checkpatch
2022-09-19 8:59 ` 0-day Robot [this message]
2022-09-19 8:45 |FAILURE| pw116416 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-09-19 8:45 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=20220919085956.3994388-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=yidingx.zhou@intel.com \
/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).