On Thu, Dec 13, 2018 at 02:02:58PM +0100, Paul Gevers wrote: > Hi Wouter, > > Sorry it took so long for you to get a reply on this. I didn't feel > competent enough to respond, but apparently nobody else felt like > replying either.
No worries. > On Fri, 07 Sep 2018 21:36:34 +0200 Wouter Verhelst <[email protected]> > wrote: > > I'm thinking of adding autopkgtests to src:nbd. > > Great. > > <Great explanation of what you think is your problem and how it could be > solved> > > > Thoughts? > > To be honest, this feels like lots of work for a tiny corner case. I'm not sure it's a tiny corner case. The original thing that I thought of (which is not what I proposed in the bug report) would have been, but I simplified it a lot. This proposal would allow testing of any network-based system; e.g., it would allow test suites to test that auto-detecting things on the network will work (cups, routing software, avahi stuff, etc), or that a piece of client/server software that has issues with the client running on the same host as the server works correctly. > Therefor, I don't expect anybody to take this on soon, except if you do > that yourself. I can do that. > And still, the code must be supported, autopkgtest is already quite > big. Sure. > One thing I note on your proposal, autopkgtest takes care by itself if > testbeds can be reused or not. I am not sure if you want testbed2 in > your example to be really the same testbed, or if testbed2 is just > semantics for "another testbed than testbed1". I'm honestly not sure anymore, it's been a while since I wrote that up... -- To the thief who stole my anti-depressants: I hope you're happy -- seen somewhere on the Internet on a photo of a billboard
