From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com, robot@bytheb.org
Subject: |FAILURE| pw128464 [PATCH v2] doc: prefer installing using meson rather than ninja
Date: Fri, 9 Jun 2023 10:39:44 -0400 [thread overview]
Message-ID: <20230609143944.486589-1-robot@bytheb.org> (raw)
In-Reply-To: <20230609133406.80093-1-bruce.richardson@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/128464/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5222545884
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
Port 1 is closed
Done
Bye...
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ != true ]
+ [ true = true ]
+ cat libabigail/VERSION
+ [ libabigail-2.1 != libabigail-2.1 ]
+ [ ! -d libabigail ]
+ pwd
+ export PATH=/home/runner/work/dpdk/dpdk/libabigail/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/snap/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
+ REF_GIT_REPO=https://dpdk.org/git/dpdk
+ cat reference/VERSION
+ [ v23.03 != v23.03 ]
+ [ ! -d reference ]
+ pwd
+ DESTDIR=/home/runner/work/dpdk/dpdk/install meson -C build install
usage: meson [-h]
{setup,configure,dist,install,introspect,init,test,wrap,subprojects,help,rewrite}
...
meson: error: unrecognized arguments: -C
##[error]Process completed with exit code 2.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-06-09 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230609133406.80093-1-bruce.richardson@intel.com>
2023-06-09 13:23 ` |SUCCESS| " qemudev
2023-06-09 13:27 ` qemudev
2023-06-09 13:35 ` checkpatch
2023-06-09 14:39 ` 0-day Robot [this message]
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=20230609143944.486589-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=bruce.richardson@intel.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).