Source: libmodulemd Version: 2.14.0-3 Severity: important User: debian...@lists.debian.org Usertags: flaky X-Debbugs-Cc: debian...@lists.debian.org
The libmodulemd autopkgtest 'module_index_merger_debug' intermittently fails on the riscv64 runners on ci.debian.net, which the testing migration infrastructure assumes is a regression in a package that was upgraded, preventing packages like glib2.0 and meson from migrating to testing until the libmodulemd autopkgtest is retried. For example, please see: https://ci.debian.net/packages/libm/libmodulemd/testing/riscv64/55201008/ https://ci.debian.net/packages/libm/libmodulemd/testing/riscv64/54969981/ https://ci.debian.net/packages/libm/libmodulemd/testing/riscv64/54604298/ When the test succeeds, it generally takes around 60 to 100 seconds on riscv64, which is uncomfortably close to the timeout, so I think it might just be that slow. Probably running `meson test --timeout-multiplier=10` (as the debian/rules seems to do) would help? Thanks, smcv
