Bug#852820 closed by Guillem Jover <email@example.com> (Bug#852820: fixed in dpkg 1.18.21)
- Subject: Bug#852820 closed by Guillem Jover <firstname.lastname@example.org> (Bug#852820: fixed in dpkg 1.18.21)
- From: email@example.com (Iain Lane)
- Date: Thu, 16 Feb 2017 11:11:58 +0000
- Message-id: <[🔎] 20170216111158.butoj7szcjn4zsqx@nightingale>
- In-reply-to: <handler.852820.D852820.firstname.lastname@example.org>
- References: <E1cXwPW-0005dG-Oc@fasolo.debian.org> <email@example.com> <handler.852820.D852820.firstname.lastname@example.org>
On Sun, Jan 29, 2017 at 08:51:07PM +0000, Debian Bug Tracking System wrote:
> * Revert "Generate Testsuite-Restrictions fields from the test restrictions
> in dpkg-source into .dsc files". This change is contentious and should
> have been discussed more widely. Given that this has been live only for
> a couple of days, the impact should be minimal, but still something to
> take into account once and if this gets reintroduced. Closes: #852820
I didn't actually notice (because I didn't receive the -done or the
"pending" mail) that this was reverted until just now when I came to
start building on the field.
I feel a bit frustrated. It would have been quite helpful to have the
change in the next stable but I suppose there is now not much chance of
whatever eventual solution making it there.
What is my way forward? My goal is to be able to dispatch tests to LXD
if all of the tests can be run there, or to the SSH runner (nova)
otherwise. To do that I would have compared the Testsuite-Restrictions
field to those I know that LXD doesn't support ('isolation-machine').
The mechanism which dispatches the tests (for us it's britney) doesn't
have the source package to hand. I would have to write code to download,
unpack, parse, cleanup, deal with errors, etc. And live with a large
slowdown. Or alternatively I would have to maintain another service to
somehow supply this information by a side channel, with all the
attendant complexity that would involve.
Is there a non terrible way to handle this in dpkg-source? That would
really be quite helpful.
Otherwise, maybe in autopkgtest we could add a 'fail fast' mode that
checks all the restrictions against the features in the selected runner
and reports via a new exit code if they can't all be run. I'm not sure
what kind of overhead we'd be talking about here in the failure case,
but definitely more than being able to DTRT off the bat.
Iain Lane [ iain at orangesquash.org.uk ]
Debian Developer [ laney at debian.org ]
Ubuntu Developer [ laney at ubuntu.com ]
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: not available