From: Cyril Hrubis <chrubis@suse.cz>
To: Jiri Jaburek <jjaburek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] network namespaces tests cleanup
Date: Tue, 17 Feb 2015 16:20:34 +0100 [thread overview]
Message-ID: <20150217152034.GA26897@rei> (raw)
In-Reply-To: <54E35175.20807@redhat.com>
Hi!
> $ ip netns add testns
>
> and the following two have to return different IDs:
>
> $ readlink /proc/self/ns/net
> net:[4026531969]
>
> $ ip netns exec testns readlink /proc/self/ns/net
> net:[4026532368]
>
> (And the kernel tests would ideally ensure that different procfs/ns
> values *really* result in different namespaces based on tested
> behavior.)
That sounds reasonable and easy enough.
> > Agree that the kernel functionality is the same. But how does having two
> > different testcases one for kernel functionality and one for ip decrease
> > maintenance ratio? This soulution would IMHO be more complicated. The
> > coverate should be same. The only aspect in which this solution is
> > likely better is test runtime, but that shouldn't be a problem because
> > these testcases does not take long time. Or am I mistaken?
>
> Right now, they don't (IIRC), but will you document it? Will you watch
> for future tests added to this area, to make sure they don't take a long
> time because of this "hack"? I guess these are the maintenance costs
> I'm trying to point out.
This sounds reasonable as well.
> In the end, my suggestion was really just a suggestion - each approach
> has pros and cons and it's up to the author (and you, as an upstream
> maintainer) to pick the one you want.
And I'm certainly willing to listen to anybody with good ideas ;).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-02-17 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <789026778.7588485.1423581396876.JavaMail.zimbra@redhat.com>
[not found] ` <1688764619.7589818.1423581433749.JavaMail.zimbra@redhat.com>
2015-02-12 11:03 ` [LTP] network namespaces tests cleanup Cyril Hrubis
[not found] ` <980241572.9316983.1423749665613.JavaMail.zimbra@redhat.com>
[not found] ` <54E33EE9.9000302@redhat.com>
2015-02-17 14:04 ` Cyril Hrubis
[not found] ` <54E35175.20807@redhat.com>
2015-02-17 15:20 ` Cyril Hrubis [this message]
2015-02-18 16:54 ` Jiri Jaburek
2015-02-18 17:35 ` Jiri Jaburek
2015-02-19 15:04 ` Cyril Hrubis
[not found] ` <54EC5053.4060005@redhat.com>
2015-02-25 12:35 ` Cyril Hrubis
[not found] ` <54EDC5B4.9050806@redhat.com>
2015-02-25 13:05 ` Cyril Hrubis
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=20150217152034.GA26897@rei \
--to=chrubis@suse.cz \
--cc=jjaburek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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.