Antonio Terceiro writes ("Bug#901030: some context"):
> the problem here is that by definition, some types of testbed don't
> allow you to test some packages.
Right, but in principle these testbeds could. All that is needed is
to install binfmt-misc in the host. I am sugges
On Tue, Jun 12, 2018 at 02:34:57PM +0200, Hans-Christoph Steiner wrote:
>
> I agree that there can't be a Restriction for every config under the
> sun. I'm thinking more like Ian, where there can be some useful chunks
> with a finer grain than "needs isolation".
Allowing a test definition to cau
Hans-Christoph Steiner writes ("Bug#901030: some context"):
> I agree that there can't be a Restriction for every config under the
> sun. I'm thinking more like Ian, where there can be some useful chunks
> with a finer grain than "needs isolation".
>
I agree that there can't be a Restriction for every config under the
sun. I'm thinking more like Ian, where there can be some useful chunks
with a finer grain than "needs isolation".
I think that autopkgtest will never work well for a lot of packages with
such a inflexible system for specifying
Antonio Terceiro writes ("Bug#901030: some context"):
> Control: severity -1 wishlist
> Control: tag -1 + wontfix
..
> By the same argument we would need one restriction for every
> kernel-related feature out there. Implementing every type of special
> snow flake config
Control: severity -1 wishlist
Control: tag -1 + wontfix
On Fri, Jun 08, 2018 at 12:35:13PM +0200, Hans-Christoph Steiner wrote:
>
> This issue was discovered while working on getting autopkgtest running
> smoothly in Docker containers running in Gitlab CI on salsa.debian.org:
> https://salsa.debi
This issue was discovered while working on getting autopkgtest running
smoothly in Docker containers running in Gitlab CI on salsa.debian.org:
https://salsa.debian.org/salsa/support/issues/27
When running autopkgtest in a gitlab-ci docker container, it can run
directly in it since it has root ac
7 matches
Mail list logo
