Hi, sorry for the delay. Initially I wanted to include all tests in the packaging as they just didn't fail for me on ppc64el, amd64 and i386. Having a look at the .spec file upstream, they skip some of the tests, amongst them, the one we have an issue with.
--- # don't require qemu within OBS # and exclude known flaky tests in OBS check # https://progress.opensuse.org/issues/52652 # 07-commands: https://progress.opensuse.org/issues/60755 for i in 07-commands 13-osutils 14-isotovideo 18-qemu-options 18-backend-qemu 99-full-stack; do rm t/$i.t done --- So I think we can safely skip them, if upstream does. I'm going to change this. Fred On Sat, 27 Mar 2021 17:12:17 +0200, Adrian Bunk <b...@debian.org> wrote: > ping > > > On Fri, Mar 12, 2021 at 05:33:27PM +0200, Adrian Bunk wrote: > > On Thu, Feb 25, 2021 at 09:52:08AM +0100, Paul Gevers wrote: > > > Control: found -1 4.5.1527308405.8b586d5-4.2 > > > > > > Hi Frédéric, Hideki, > > > > > > On 17-02-2021 22:01, Paul Gevers wrote: > > > > If the forth time worked because of sheer luck, then please no, keep the > > > > bug open until the build is less flaky. We need packages to be build > > > > without failure [1]. Having to baby-sit flaky is not really an option as > > > > there are too many packages in the Debian archive. > > > > > > I had a look at the reproducible build project history for os-autoinst > > > [1] and the package FTBFS very, very often, both in unstable and > > > testing. I have marked this bug as found, so now this package is able to > > > migrate, *but* you'll have to fix this bug if you want the package to > > > ship with bullseye. If you can't fix the tests and still believe that > > > the package is in a good shape for the bullseye release, I suggest you > > > disable the tests for now. > > > > Or if the package is not in a good shape on i386, > > remove it from the architecture list. > > > > os-autoinst is amd64-only in buster. > > > > > Paul > > >... > > > > cu > > Adrian >
signature.asc
Description: PGP signature
