Hi Paul, Paul Gevers <elb...@debian.org> writes:
> Source: vorta > Version: 0.9.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest of your package because it > was blocking the migration of xorg-server. I noticed that it regularly > fails, at least on ppc64el, but the same failure happens on all > architectures. Thank you for this report--especially because backup software should be provably reliable! 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. In the past upstream has maintained that PyQt causes a lot of flakyness, and it doesn't look like our PyQt package or xorg-server has autopkgtests enabled. The reason why xorg-server would be blocked is presumably because we're currently using "xvfb" to run autopkgtests on this GUI package. Is the use of "xvfb" still best practices, or should it be switched to use something else? I build Vorta a couple of times before releasing, I manually check on DebCI and reprobuilds periodically, and I've haven't been able to identify any flaky amd64 autopkgtests. Please note one newly disabled test in 0.9.1-2 and vorta_0.10.0~beta1-1~exp1. That one recently began to consistently fail on my system during autopkgtests: something changed in the test environment, but I haven't had time to investigate. > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. I noticed that borgbackup's tests now fail on reprobuilds, and I suspect recent upstream-Python changes to date handling, timezone, and or locale. > Don't hesitate to reach out if you need help and some more information > from our infrastructure. Is there a NEWS file or changelog that I can follow to remain appraised of what our infra is fuzzing for and what changes have been made? Regards, Nicholas
signature.asc
Description: PGP signature
