Hi, Charles, On الأحد 12 تـمـوز 2015 04:05, Charles Plessy wrote:
for some packages it is doable to run the tests at build time and also distribute them in a binary package that is used for the autopkgtests and for users to troubleshoot their own installations. See samtools for example. In other cases (Perl packages, R packages), the tests seem to be too much part of the build system to be easily packaged exhaustively in a stand-alone way. Or it is just that I never found how... For python-pysam, I think that I could start the packaged test suite in the past. Sorry that I did not have time to follow your work in details; is this package is now broken then it makes sense to remove it, otherwise I would argue that it is useful and should be kept.
Even if it is broken as far as autopkgtest is concerned, it could still have some utility for the user. Then, the independent tests/control file could be used for autopkgtest and the python-pysam-tests package can left for the user.
Lastly, sometimes for some pacakges (for instance bedtools), the regression tests never passed fully on Debian. This makes them less useful, but at least, they can be monitored to spot regressions, where even more tests would fail.
That is interesting. For bedtools, is that a problem with the test suite or with the packaging? I didn't think that a package could be uploaded to somewhere besides experimental while it is known to be failing tests.
Regards, Afif -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55a2c433.4070...@ghraoui.name