From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wathsala.vithanage@arm.com, robot@bytheb.org
Subject: |FAILURE| pw136796 [PATCH v2] net/mlx5: enable PCI related counters
Date: Wed, 14 Feb 2024 16:04:32 -0500 [thread overview]
Message-ID: <20240214210432.679978-1-robot@bytheb.org> (raw)
In-Reply-To: <20240214201455.1388720-1-wathsala.vithanage@arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/136796/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7906987903
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
make[2]: Nothing to be done for 'install-exec-am'.
/usr/bin/mkdir -p '/home/runner/work/dpdk/dpdk/libabigail/lib/libabigail'
/usr/bin/install -c -m 644 ../default.abignore '/home/runner/work/dpdk/dpdk/libabigail/lib/libabigail'
/usr/bin/mkdir -p '/home/runner/work/dpdk/dpdk/libabigail/share/aclocal'
/usr/bin/install -c -m 644 ../abigail.m4 '/home/runner/work/dpdk/dpdk/libabigail/share/aclocal'
/usr/bin/mkdir -p '/home/runner/work/dpdk/dpdk/libabigail/lib/pkgconfig'
/usr/bin/install -c -m 644 libabigail.pc '/home/runner/work/dpdk/dpdk/libabigail/lib/pkgconfig'
make: Leaving directory '/home/runner/work/dpdk/dpdk/libabigail-2.4/build'
+ rm -rf libabigail-2.4
+ rm libabigail-2.4.tar.xz
+ echo libabigail-2.4
+ pwd
+ export PATH=/home/runner/work/dpdk/dpdk/libabigail/bin:/snap/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:/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.11 ]
+ rm -rf reference
+ [ ! -d reference ]
+ pwd
+ readlink -f /home/runner/work/dpdk/dpdk/../dpdk-v23.11
+ refsrcdir=/home/runner/work/dpdk/dpdk-v23.11
+ git clone --single-branch -b v23.11 https://dpdk.org/git/dpdk /home/runner/work/dpdk/dpdk-v23.11
Cloning into '/home/runner/work/dpdk/dpdk-v23.11'...
fatal: unable to access 'https://dpdk.org/git/dpdk/': The requested URL returned error: 504
##[error]Process completed with exit code 128.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2024-02-14 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240214201455.1388720-1-wathsala.vithanage@arm.com>
2024-02-14 19:56 ` |SUCCESS| " qemudev
2024-02-14 20:00 ` qemudev
2024-02-14 20:15 ` checkpatch
2024-02-14 21:04 ` 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=20240214210432.679978-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=wathsala.vithanage@arm.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).