From: Brandon Lo <blo@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab@iol.unh.edu, ci@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-ci] [dpdklab] Re: Build failure with opensuse
Date: Mon, 2 Mar 2020 11:25:46 -0500 [thread overview]
Message-ID: <CAOeXdvbsJyBHBmaqsh11+1jHpZONa+=Q199MVXFtNtUSEo-e4Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yqHFpHgeVWVVyA+5wZ=vsgq5eUhgHA+88mcqmDYsugJw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2277 bytes --]
Hi David,
We have looked into the openSUSE compile errors.
The issue was discovered to be related to Podman and have been resolved;
we are now rerunning all tests that have been affected.
Please give it a moment to complete all tests.
As for the scripts used for starting the test, I have attached a zip that
contains scripts used to kick off the tests.
However, our team does still need to come up with a way to submit script
changes to the project.
Thanks
On Mon, Mar 2, 2020 at 9:38 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Mon, Mar 2, 2020 at 3:22 PM David Marchand <david.marchand@redhat.com>
> wrote:
> >
> > 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.
>
> And as a bonus, where can I find those scripts?
> It would be easier to look into this kind of issue, or remove build
> options that are dead, like CONFIG_RTE_EAL_ALLOW_INV_SOCKET_ID [1]
> which is still set by this script.
>
> Thanks.
>
>
> 1:
> https://git.dpdk.org/dpdk/commit/?id=8e35792c5325f9fd2cb7cfab507aa23fc956ced7
>
> --
> David Marchand
>
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
[-- Attachment #1.2: Type: text/html, Size: 4660 bytes --]
[-- Attachment #2: dpdklab_scripts.zip --]
[-- Type: application/zip, Size: 25454 bytes --]
next prev parent reply other threads:[~2020-03-02 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 14:22 [dpdk-ci] " David Marchand
2020-03-02 14:37 ` David Marchand
2020-03-02 16:25 ` Brandon Lo [this message]
2020-03-02 18:13 ` [dpdk-ci] [dpdklab] " 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='CAOeXdvbsJyBHBmaqsh11+1jHpZONa+=Q199MVXFtNtUSEo-e4Q@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=bluca@debian.org \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--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).