DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] False alarm on CI lab.dpdk.org
Date: Tue, 6 Oct 2020 10:14:57 -0400	[thread overview]
Message-ID: <CAOeXdvZSJF0Se0mzrfdph8XBfwUjOndmFaCoce9x-u2LWQEj7Q@mail.gmail.com> (raw)
In-Reply-To: <BY5PR11MB4451721EFE6BC032F40E3AA6F8310@BY5PR11MB4451.namprd11.prod.outlook.com>

Hi Nic,

I appreciate the report; I have looked into the issue and fixed it.
Patchsets affected will be reran.

Thanks,
Brandon

On Fri, Oct 2, 2020 at 1:48 PM Chautru, Nicolas
<nicolas.chautru@intel.com> wrote:
>
> Hi,
>
>
>
> Seeing a CI issue here not related to the related patchset :
>
> https://lab.dpdk.org/results/dashboard/patchsets/13420/
>
>
>
> + podman run --rm -v /home-local/jenkins-local/jenkins-agent/workspace/openSuse-Leap-Compile-DPDK-Meson/dpdk:/dpdk:Z --entrypoint /compile_meson.sh opensuse-leap15/dpdk_compile
>
> Error: /usr/bin/slirp4netns failed: "sent tapfd=7 for tap0\nWARNING: Support for sandboxing is experimental\nWARNING: Support for seccomp is experimental\nreceived tapfd=7\ncannot remount / as read-only\nenable_seccomp failed\ndo_slirp is exiting\ndo_slirp failed\nparent failed\nWARNING: Support for sandboxing is experimental\nWARNING: Support for seccomp is experimental\nStarting slirp\n* MTU:             65520\n* Network:         10.0.2.0\n* Netmask:         255.255.255.0\n* Gateway:         10.0.2.2\n* DNS:             10.0.2.3\n* Recommended IP:  10.0.2.100\nseccomp: The following syscalls will be blocked by seccomp:"
>
> [126] Error running command.
>
>
>
> Apologize if already reported.
>
> Nic



-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

      reply	other threads:[~2020-10-06 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 17:47 Chautru, Nicolas
2020-10-06 14:14 ` Brandon Lo [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=CAOeXdvZSJF0Se0mzrfdph8XBfwUjOndmFaCoce9x-u2LWQEj7Q@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=nicolas.chautru@intel.com \
    /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).