From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ktejasree@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw124472 [PATCH v3] examples/ipsec-secgw: set AES-CTR IV length to 16
Date: Thu, 23 Feb 2023 13:19:19 -0500 [thread overview]
Message-ID: <20230223181919.1681881-1-robot@bytheb.org> (raw)
In-Reply-To: <20230223154306.2807523-1-ktejasree@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/124472/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4254454037
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
/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.1/build'
+ rm -rf libabigail-2.1
+ rm libabigail-2.1.tar.gz
+ echo libabigail-2.1
+ 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-stable
+ cat reference/VERSION
+ [ != v22.11.1 ]
+ rm -rf reference
+ [ ! -d reference ]
+ pwd
+ readlink -f /home/runner/work/dpdk/dpdk/../dpdk-v22.11.1
+ refsrcdir=/home/runner/work/dpdk/dpdk-v22.11.1
+ git clone --single-branch -b v22.11.1 https://dpdk.org/git/dpdk-stable /home/runner/work/dpdk/dpdk-v22.11.1
Cloning into '/home/runner/work/dpdk/dpdk-v22.11.1'...
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: the remote end hung up unexpectedly
##[error]Process completed with exit code 128.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2023-02-23 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223154306.2807523-1-ktejasree@marvell.com>
2023-02-23 15:31 ` |SUCCESS| " qemudev
2023-02-23 15:35 ` qemudev
2023-02-23 15:43 ` checkpatch
2023-02-23 18:19 ` 0-day Robot [this message]
2023-02-23 16:35 |FAILURE| pw124472 [PATCH] [v3] " 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=20230223181919.1681881-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=ktejasree@marvell.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).