Control: forwarded -1 https://github.com/borgbase/vorta/issues/2119

Hi,

tldr: Upstream has temporarily disabled the offending test pending
investigation, and this bug will be resolved momentarily.  Meanwhile
xorg migrated just fine.  Reply follows inline

Paul Gevers <elb...@debian.org> writes:

> On 01-11-2024 00:04, Nicholas D Steeves wrote:
>> Where can I find more information about these
>> alleged flaky amd64 autopkgtests.  As far as I an tell the current
>> issues are related to python3-defaults from experimental.
>
> E.g. https://ci.debian.net/packages/v/vorta/testing/amd64/53739823/
> (found trivially from https://ci.debian.net/packages/v/vorta/testing/amd64/)

Thank you.  I had been monitoring logs for unstable and hadn't realised
that DebCI used a different strategy for testing.  I'll keep an eye on
it in the future.

> I'm not sure what you mean with fuzzing. My normal understanding of that 
> word doesn't apply to what we do.

Maybe the various upstreams who have used the word "fuzzing" when
referring to DebCI and reprobuilds have different standards than we do?
For example when we test every supported Python version, and then test
mixes of packages from unstable, testing, and experimental, the
upstreams I'm familiar with will tend to test a single stack for
GNU/Linux.

> There is no specific file to follow on our configuration changes, but 
> you could watch for commits here:
> https://salsa.debian.org/ci-team/debian-ci-config/

Thank you for the link.  Ouf, it would take many spoons to remain
appraised...

Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to