From: Harald Welte <laforge@gnumonks.org>
To: Andreas Schultz <aschultz@tpip.net>
Cc: Pablo Neira Ayuso <pablo@gnumonks.org>,
netdev <netdev@vger.kernel.org>,
osmocom-net-gprs <osmocom-net-gprs@lists.osmocom.org>
Subject: Re: RFC: unit tests for kernel GTP module
Date: Fri, 17 Feb 2017 19:03:16 +0100 [thread overview]
Message-ID: <20170217180316.ujzsbnb2s2ee44iw@nataraja> (raw)
In-Reply-To: <1507789126.143172.1487343779235.JavaMail.zimbra@tpip.net>
Hi Andreas,
On Fri, Feb 17, 2017 at 04:02:59PM +0100, Andreas Schultz wrote:
> The test suite is proprietary, so we can only share the results but
> not the test setup itself.
it would be great to have some CI setup where both current stable as
well as a development branch of the code is tested, and reports
published regularly. Not sure how realistic that is.
> We more or less removed static GTP tunnels. The tools in libgtpnl
> only work when an application is keeping the GTP socket alive.
Well, then those tools need to be adapted accordingly. That's what I
also indicated in other mails: Changes in the kernel GTP code should
always be followed-up with correspondign changes in libgtpnl and
associated tools. I mean, the tool could just open the socket and then
continue to run until terminated explicitly...
I think there's a lot of value in some very low-level tools for testing
and experimentation, without the complexity of configuring + running an
Erlang GGSN/P-GW with all its dependencies.
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
prev parent reply other threads:[~2017-02-17 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:08 RFC: unit tests for kernel GTP module Harald Welte
2017-02-17 10:22 ` Ido Schimmel
2017-02-17 15:02 ` Andreas Schultz
2017-02-17 18:03 ` Harald Welte [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=20170217180316.ujzsbnb2s2ee44iw@nataraja \
--to=laforge@gnumonks.org \
--cc=aschultz@tpip.net \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@gnumonks.org \
/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