Hi, On Dienstag, 21. Januar 2014, Jakub Wilk wrote: > * Holger Levsen <[email protected]>, 2014-01-21, 16:23: > >instead of running the test suite at build time, how about adding > >autopkgtests > adequate does have autopkgtests. :-)
heh - I'm not surprised at all actually :) > >and run the test suite on new uploads on ci.debian.net? > I didn't know about ci.d.n. me neither until the mini debconf in Paris... > Let me see… The latest log[0] reads: > | Need to get 30.0 kB of source archives. > | Err http://ftp.us.debian.org/debian/ unstable/main adequate 0.11.3 (dsc) > | > | 404 Not Found [IP: 64.50.236.52 80] > | > | Err http://ftp.us.debian.org/debian/ unstable/main adequate 0.11.3 (tar) > | > | 404 Not Found [IP: 64.50.236.52 80] > Oops. that could be a problem in ci.d.n, which is pretty new - currently half the autotests there fail, while the packages are not *that* broken :) cc:ing terceiro so he can comment on this. > The reason I wanted to run the testsuite at build time (in addition to > autopkgtests) are: > > 1) I sometimes forget to run the testsuite before uploading. But OTOH I > never forget to build the package before uploading it. ;-) :-) another random idea: the testsuite could download some (auto generated) chroot tarball and test adequate on that?! > 2) When I filed the bug, there was no infrastructure to automatically > run DEP-5 tests archive-wide. I see things improved in this area, but > we're not quite there yet. dep-5 is about machine readable debian/copyright, I dont see how this relates...? cheers, Holger
signature.asc
Description: This is a digitally signed message part.
