Re: bitseq - Clarification on autopkgtest setup for 32-bit.
On 12 June 2025 10:04:23 am IST, Ananthu C V <weepingclown@disroot.org> wrote:
>Hi,
>
>On 11 June 2025 20:59:00 UTC, "Étienne Mollier" <emollier@debian.org> wrote:
>
>>Once the skip is
>>implemented, you should see autopkgtest skip on i386, while
>>amd64 runs should still pass:
>>
>> $ autopkgtest bitseq_0.7.5+dfsg-8_i386.changes -- unshare --arch i386 --release unstable
>> […]
>> autopkgtest [22:23:57]: build not needed
>> run-unit-test SKIP Test declares architecture as not supported: i386
>> […]
>>
>>Such output is the expected result from the maneuver. If we're
>>lucky, this may be sufficient to allow bitseq to migrate.
>I am not fully sure about this, but I don't think skipped tests are considered successful. That will then call for a manual unblock from the RT at this point of freeze for the package to migrate, since the package won't be getting the autopkgtest bounty benefits
Didn't really try but if we were to use bowtie to generate data locally and use that data for autopkgtest instead of running bowtie during autopkgtest, that would help to test the package for all archs.
A note in d/t/README.Debian explaining how the test data is generated from source should be enough.
Best,
Nilesh
Reply to: