From thozza at redhat.com Mon Oct 21 08:14:50 2013 From: thozza at redhat.com (Tomas Hozza) Date: Mon, 21 Oct 2013 04:14:50 -0400 (EDT) Subject: [ldns-users] Tests in the ldns tarball In-Reply-To: <953913052.6765394.1382342919313.JavaMail.root@redhat.com> Message-ID: <1873363277.6766158.1382343290162.JavaMail.root@redhat.com> Hi. I have been investigating tests in packages I maintain in Fedora and found out that ldns seems to have tests, but they are not distributed in the tarball. $ make test if test -x "`which bash`"; then bash test/test_all.sh; else sh test/test_all.sh; fi bash: test/test_all.sh: No such file or directory make: *** [test] Error 127 I wanted to ask what is the reason for not including tests in the tarball? I would like to run tests during each package build if they are available. Would it be possible to include tests in the (tarball) of future release of ldns? Thank you. Regards, Tomas Hozza From willem at nlnetlabs.nl Tue Oct 22 12:56:46 2013 From: willem at nlnetlabs.nl (Willem Toorop) Date: Tue, 22 Oct 2013 14:56:46 +0200 Subject: [ldns-users] Tests in the ldns tarball In-Reply-To: <1873363277.6766158.1382343290162.JavaMail.root@redhat.com> References: <1873363277.6766158.1382343290162.JavaMail.root@redhat.com> Message-ID: <5266760E.30503@nlnetlabs.nl> op 21-10-13 10:14, Tomas Hozza schreef: > I wanted to ask what is the reason for not including tests in the > tarball? I would like to run tests during each package build if > they are available. Would it be possible to include tests in the > (tarball) of future release of ldns? Hi Tomas, I use the tests for continuous integration. On each push to the git repository, our CI-server checks out the latest commit and executes test/test_ci.sh. I also use them to asses portability of ldns. Not all tests are suitable for inclusion; For example the unbound-regressions test assumes you have an unbound installed compiled against a previous version of ldns. Tests that check for code style are probably less interesting for you. Also the tests are packaged in tpkg package format, for which you need the tpkg program. Which, I believe, is not (yet) in a public repository. (Though you can unpack them with "tar xz"). I can see the value of having unit tests in the tarball though, but it will need a bit of work to elliminate the environmental requirments... If you want to have a look at the tests now, you can check out the ldns repository from git (i.e. git clone http://git.nlnetlabs.nl/ldns ) and unpack the .tpkg files in the test directory with tar. -- Willem From Ray.Bellis at nominet.org.uk Thu Oct 31 08:38:13 2013 From: Ray.Bellis at nominet.org.uk (Ray Bellis) Date: Thu, 31 Oct 2013 08:38:13 +0000 Subject: [ldns-users] new to ldns In-Reply-To: <5214966E.70709@nlnetlabs.nl> References: <5214966E.70709@nlnetlabs.nl> Message-ID: <53F00E5CD8B2E34C81C0C89EB0B4FE736854E486@wds-exc2.okna.nominet.org.uk> On 21 Aug 2013, at 11:29, Willem Toorop > wrote: Hi Gagandeep, ?Ond?ej is right, it would be helpful if you tell a bit more about the kind of name server you wish to create. That said, ldns might be appropriate for small and simple nameservers that do something peculiar (and are not for production purposes). Within the examples section of the ldns source code is a simple fake nameserver tool for testing and debugging: ldns-testns. We use it in unbounds unit tests and also in experimental setups (for example in our Path MTU black-holes research). You could study its source to get you started. With apologies for resurrecting an old thread, you can find the "evldns" package I wrote for creating small bespoke DNS servers that uses ldns and libevent at . It's good for servers where you can compute a response synchronously in real-time. Hence no good (yet) for recursive servers, but you can already do some pretty funky stuff with it. Ray -------------- next part -------------- An HTML attachment was scrubbed... URL: