From: David Marchand <david.marchand@redhat.com>
To: dpdklab@iol.unh.edu
Cc: ci@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: [dpdk-ci] Build failure with opensuse
Date: Mon, 2 Mar 2020 15:22:52 +0100 [thread overview]
Message-ID: <CAJFAV8y8bUB3txWJrP=KVv3Xf0JqpH13i-QxYZxyFO0Yt87Bog@mail.gmail.com> (raw)
Looking at a series from Luca, I found build errors for opensuse:
http://mails.dpdk.org/archives/test-report/2020-February/118961.html
The splat is:
An uncaught exception was raised. We may already know about the issue.
If your patch is not run again after one business day, feel free to
contact us to let us know.
Traceback (most recent call last):
File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 48, in <module>
compile_dpdk.build()
File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 35, in build
self.image_build(image)
File "/opt/dpdklab/dpdklab-ci/ci.py", line 202, in image_build
cwd=script_dir + '/containers')
File "/opt/dpdklab/dpdklab-ci/ci.py", line 180, in check_call
subprocess.check_call(command, **kwargs)
File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('podman', 'build', '-t',
'opensuse-leap15/dpdk_compile', '-f',
'opensuse-leap15/dpdk_compile.Dockerfile', '.')' returned non-zero
exit status 1.
Is this being looked at?
Thanks.
--
David Marchand
next reply other threads:[~2020-03-02 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 14:22 David Marchand [this message]
2020-03-02 14:37 ` David Marchand
2020-03-02 16:25 ` [dpdk-ci] [dpdklab] " Brandon Lo
2020-03-02 18:13 ` Thomas Monjalon
2020-03-03 9:00 ` David Marchand
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='CAJFAV8y8bUB3txWJrP=KVv3Xf0JqpH13i-QxYZxyFO0Yt87Bog@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/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).