From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] netns_netlink test failure
Date: Mon, 2 Mar 2020 13:41:23 +0800 [thread overview]
Message-ID: <42474632-110d-bf91-f9da-37b16f8e6fed@cn.fujitsu.com> (raw)
In-Reply-To: <MAXPR0101MB1468032C8109347B258800B7EEE70@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
Hi
> Hi,
> What could be the possible reason behind failing,any guess??
At lease, you should attach this command output.
# ip tuntap add dev dummy0 mode tap
Best Regards
Yang Xu
> ------------------------------------------------------------------------
> *From:* Cyril Hrubis <chrubis@suse.cz>
> *Sent:* Friday, February 28, 2020 2:51 PM
> *To:* Pankaj Vinadrao Joshi <Pankaj.VJ@exaleapsemi.com>
> *Cc:* ltp@lists.linux.it <ltp@lists.linux.it>
> *Subject:* Re: [LTP] netns_netlink test failure
> Hi!
>> <<<test_output>>>
>> open: No such file or directory
>> netns_netlink??? 1? TBROK? :? netns_netlink.c:143: system() failed
> ???????????????????????????????????????????????? ^
> ???????????????????????????????????????????????? This is a line number,
> ???????????????????????????????????????????????? if you look a the
> ???????????????????????????????????????????????? source code of the
> ???????????????????????????????????????????????? test, you see:
>
> ??????? if (WEXITSTATUS(system("ip tuntap add dev dummy0 mode tap")))
> ??????????????? tst_brkm(TBROK, cleanup, "system() failed");
>
> So that the failed command was "ip tuntap add dev dummy0 mode tap", it's
> up to
> you to figure out why...
>
> --
> Cyril Hrubis
> chrubis@suse.cz
> [EXT]
>
>
next prev parent reply other threads:[~2020-03-02 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 7:14 [LTP] netns_netlink test failure Pankaj Vinadrao Joshi
2020-02-28 9:21 ` Cyril Hrubis
2020-03-02 4:32 ` Pankaj Vinadrao Joshi
2020-03-02 5:41 ` Yang Xu [this message]
[not found] ` <MAXPR0101MB14686629CA22EDA8E38CBE6AEEE70@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
2020-03-02 8:08 ` Yang Xu
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=42474632-110d-bf91-f9da-37b16f8e6fed@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.