Source: xsnow Version: 1:3.8.3-1 Severity: important X-Debbugs-Cc: [email protected] User: [email protected] Usertags: riscv64 User: [email protected] Usertags: flaky
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/ >305s NOT FOUND: id-NoTrees ... >311s NOT FOUND: id-Stars ... >316s NOT FOUND: id-ShowBirds (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/ >221s Cannot create transparent window >221s Using root window >221s Using double buffer: 0x400001. 1280x1024 >221s Snowing in 0x21f: no name 0+0 1280x1024 >222s >222s (xsnow:3133): Gtk-WARNING **: 08:30:12.920: Could not load a pixbuf from >/org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg. >222s This may indicate that pixbuf loaders or the mime database could not be >found. >225s FAILED: cannot start xsnow: not found: '/home/debci/.xsnowrc' >225s /tmp/autopkgtest-lxc.m5dt1pno/downtmp/wrapper.sh: Killing leaked >background processes: 3123 3133 >225s PID TTY STAT TIME COMMAND >225s 3123 ? R 0:00 Xvfb :23.0 >225s 3133 ? Rl 0:04 /usr/games/xsnow 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
