The autopkgtest "test2.sh" frequently fails on riscv64. The failure mode
that is relevant right now is that it doesn't find some of its UI
widgets (?):

https://ci.debian.net/packages/x/xsnow/testing/riscv64/65761397/
...
...
(etc.)

and there is another failure mode where it doesn't appear to have
started at all:

https://ci.debian.net/packages/x/xsnow/unstable/riscv64/65295027/

Because this test randomly passes or fails, the autopkgtest
infrastructure assumes there's a regression in one of xsnow's
dependencies, preventing or delaying migration until the failing test is
retried.

There have also been a lot of failures on ppc64el in the past, although
those were sufficiently long ago that their logs are no longer
available.

Perhaps it's just waiting for an arbitrary time to have elapsed, and on
slower architectures like riscv64 that time is not long enough?

If possible please make this test more reliable, or if that's not
possible please mark it as flaky (see autopkgtest documentation).

    smcv

Thanks for your suggestions.

Since autopkgtest randomly fails, I guess it is a timing issue.

I'll have a look at test2.sh and upload a new version of xsnow.

Willem