Bug#993214: mpi4py: autopkgtest regression around 2021-08-25

Drew Parsons dparsons at debian.org
Sun Aug 29 23:22:02 BST 2021


On 2021-08-30 00:05, Drew Parsons wrote:
> On 2021-08-29 20:27, Graham Inggs wrote:
>> Even better would be to add the following section to 
>> debian/tests/control:
>> 
>> # Dummy test so that changes to other packages trigger our 
>> autopkgtests
>> # on ci.debian.net
>> Test-Command: /bin/true
>> Depends: libpmix-dev,
>>     libucx-dev [amd64 arm64 ppc64el],
>> Restrictions: hint-testsuite-triggers
>> 
>> Refer
>> https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
> 
> 
> That's a great idea, Graham.  I assume Lisandro will have 3.1 fixed
> soon for s390x since he's identified the cause of the failure. So I'll
> make the change in experimental rather than unstable.
> 


Graham, when I run autopkgtest, it skips the dummy test, which is what 
we want, but it does so with the message

   SKIP unknown restriction hint-testsuite-triggers


"unknown restriction", is this normal?  If so it's a bit misleading 
since the hint is not supposed to be "unknown".

Drew



More information about the debian-science-maintainers mailing list