automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: nicolas.chautru@intel.com, robot@bytheb.org
Subject: |FAILURE| pw152163 [PATCH v1 2/2] test/bbdev: update to fft test vectors
Date: Fri, 28 Feb 2025 13:07:06 -0500	[thread overview]
Message-ID: <20250228180706.3079613-1-robot@bytheb.org> (raw)
In-Reply-To: <20250228165022.480453-3-nicolas.chautru@intel.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13593283252
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-data-am'.
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.6/build'
+ rm -rf libabigail-2.6
+ rm libabigail-2.6.tar.xz
+ echo libabigail-2.6
+ 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
+ cat reference/VERSION
+ [  != v24.11 ]
+ rm -rf reference
+ [ ! -d reference ]
+ pwd
+ readlink -f /home/runner/work/dpdk/dpdk/../dpdk-v24.11
+ refsrcdir=/home/runner/work/dpdk/dpdk-v24.11
+ git clone --single-branch -b v24.11 https://dpdk.org/git/dpdk /home/runner/work/dpdk/dpdk-v24.11
Cloning into '/home/runner/work/dpdk/dpdk-v24.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-----------------------------

  parent reply	other threads:[~2025-02-28 18:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250228165022.480453-3-nicolas.chautru@intel.com>
2025-02-28 16:33 ` |SUCCESS| pw152162-152163 " qemudev
2025-02-28 16:37 ` qemudev
2025-02-28 17:01 ` |WARNING| pw152163 " checkpatch
2025-02-28 18:07 ` 0-day Robot [this message]
2025-02-28 21:50 ` |SUCCESS| pw152162-152163 [PATCH] [v1,2/2] test/bbdev: update to fft dpdklab
2025-02-28 21:52 ` dpdklab
2025-02-28 21:52 ` dpdklab
2025-02-28 22:06 ` dpdklab
2025-02-28 22:12 ` dpdklab
2025-02-28 22:14 ` dpdklab
2025-02-28 22:27 ` dpdklab
2025-03-01  0:10 ` |PENDING| " dpdklab
2025-03-01  0:30 ` |WARNING| " dpdklab
2025-03-01  0:59 ` |SUCCESS| " dpdklab
2025-03-01  0:59 ` dpdklab
2025-03-01  1:00 ` |PENDING| " 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=20250228180706.3079613-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=nicolas.chautru@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).