On Wed, Dec 01, 2021 at 08:19:20PM -0300, Antonio Terceiro wrote:
> Hi,
>
> Adding debian-python@l.d.o
>
> The context is #1000803 where Sandro asked about reducing duplication
> when running upstream test suites both during the build and under
> autopkgtest.
>
> https://bugs.debian.org/cgi-bin/
Hi,
Adding debian-python@l.d.o
The context is #1000803 where Sandro asked about reducing duplication
when running upstream test suites both during the build and under
autopkgtest.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000803
On Tue, Nov 30, 2021 at 12:47:42AM -0500, Sandro Tosi wro
> This is usually solved outside of autopkgtest itself.
>
> For example Ruby packages have a single place where tests are specified
> (debian/ruby-tests.*{rb,rake,yaml}, and the appropriate
> debian/tests/control file is autogenerated by autodep8. I would say 99%
> of Ruby packages require no dupli
On Sun, Nov 28, 2021 at 11:43:13PM -0500, Sandro Tosi wrote:
> Package: autopkgtest
> Version: 5.16
> Severity: normal
> X-Debbugs-Cc: mo...@debian.org
>
> Hello,
> There are at least 2 main places where source packages declare tests:
>
> 1. in debian/rules, to be executed at build-time
> 2. in d
Package: autopkgtest
Version: 5.16
Severity: normal
X-Debbugs-Cc: mo...@debian.org
Hello,
There are at least 2 main places where source packages declare tests:
1. in debian/rules, to be executed at build-time
2. in debina/tests/*, to be executed post-build via autopkgtests
Usually 1) are written
5 matches
Mail list logo
