Source: phyml
Version: 3:3.3.20200621-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was showing up as a regression for the upload of glibc [0]. I noticed that the test regularly fails on armel [1] in unstable, testing and stable. Somehow running the test takes significantly longer on armel than on our other ci architectures and most of the time it's getting close to the autopkgtest timeout of 2:47 h. Do you have any idea why armel would be so much slower? If the armel specific slow down can't be fixed, an autopkgtest work around could be to split the test into multiple tests, because each autopkgtest gets the timeout. Otherwise, I recommend adding an "Architecture: !armel" line to the d/t/control test stanza.

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.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] https://ci.debian.net/data/autopkgtest/testing/armel/p/phyml/24557743/log.gz
[1] https://ci.debian.net/packages/p/phyml/

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to