From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: jspewock@iol.unh.edu, robot@bytheb.org
Subject: |FAILURE| pw129502 [PATCH v4 2/2] dts: add paramiko to dependencies
Date: Wed, 12 Jul 2023 10:59:12 -0400 [thread overview]
Message-ID: <20230712145912.3884224-1-robot@bytheb.org> (raw)
In-Reply-To: <20230712140717.14856-4-jspewock@iol.unh.edu>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/129502/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5532764659
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-static-i386" failed at step Install i386 cross compiling packages
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-static-i386" at step Install i386 cross compiling packages
####################################################################################
MINI: false
PPC64LE: false
REF_GIT_TAG: v23.03
RISCV64: false
RUN_TESTS: false
##[endgroup]
+ sudo apt install -y gcc-multilib g++-multilib libnuma-dev:i386
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libnuma-dev:i386 : Depends: libnuma1:i386 (= 2.0.12-1) but it is not going to be installed
Depends: libc6-dev:i386 but it is not going to be installed or
libc-dev:i386
E: Unable to correct problems, you have held broken packages.
##[error]Process completed with exit code 100.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-static-i386" at step Install i386 cross compiling packages
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-07-12 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230712140717.14856-4-jspewock@iol.unh.edu>
2023-07-12 13:56 ` |SUCCESS| pw129501-129502 " qemudev
2023-07-12 14:00 ` qemudev
2023-07-12 14:08 ` |SUCCESS| pw129502 " checkpatch
2023-07-12 14:59 ` 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=20230712145912.3884224-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=jspewock@iol.unh.edu \
--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).