On 2016, നവംബർ 26 6:34:26 PM IST, "Jérémy Lal" <kapo...@melix.org> wrote: >Hi, > >i've been doing in all my latest uploads this setup: >- autopkgtest runs the package test suite >- build does not run tests > >Because: >1) it feels wrong to add Depends to Build-Depends, >and debian/tests/control already have all the info to properly run the >tests >2) when an autopkgtest fails, archive-wide testing reports the failure >as a package bug, >rendering tests during build useless anyway
No, that is not correct. If tests during build fails, it is rc and it is found in archive wide rebuilds. But autopkgtest failures are not rc and the bug reporting is not automatic. I know this for certain because autopkgtest for gitlab has been failing for some time. So at least in the current situation, autopkgtest is not a replacement for tests during build, it may reach that point in future, but we are not there yet. >I know that in some cases, one really need a built tree to run the >tests, >but it's not the majority. Usually a tree with patches applied is >enough. > >So please Team, don't re-add to all my packages "run tests during >build". >(and, of course, do whatever you see best when you're packaging it >yourself). This is not the right way to approach team maintained packages. If we end up differentiating "my package" and "your package", we defeat the purpose of team maintenance. Instead, we should be setting standards for the whole team, document it as team policy and implement it across all team maintained packages. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
