Hi Nilesh, On 2021-06-21 17:10, Nilesh Patra wrote: > On Mon, 21 Jun 2021 at 11:27, Andrius Merkys <[email protected] > <mailto:[email protected]>> wrote: > > Hello, > > On 2021-06-21 08:16, Andreas Tille wrote: > >>> Repository data is changed during the tests, which I dislike, > but ... > >>> well ... we need to get somewhere. > >> * And I dislike this as well, so I simply removed the build time > test, and > >> running that as autopkgtest. IMO doing this is even better since this > >> tests that the binary is actually installed. > > Another way would be to do some > > > > override_dh_auto_test: > > cp -a testdata testdata_save > > dh_auto_test > > rm -rf testdata > > mv testdata_save testdata > > > > or something like this. While I agree that autopkgtest is more > important > > than build time test both falvours make sense. > Build time tests are very important for apriori (pre-upload) detection > of breakages introduced by updates/modifications of reverse > dependencies. ratt loses much of its power without these tests. > > OK, added. > But you might want to check out ruby-team/meta[1] script, which also > checks for > autopkgtest breakeages. Admittedly, I've always liked this more. > Here's the results for this, if you'd like to have a look just as an example > > [1]: https://salsa.debian.org/ruby-team/meta > <https://salsa.debian.org/ruby-team/meta> > [2]: https://lists.debian.org/debian-med/2020/07/msg00160.html > <https://lists.debian.org/debian-med/2020/07/msg00160.html>
Thanks for letting me know - ruby-team/meta looks very helpful indeed! Best, Andrius
