Source: awesome
Version: 4.3-5
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]. It seems that it regularly fails on all architectures due to *warnings* printed on stderr. autopkgtest by default fails on output to stderr, which can be changed by adding a "allow-stderr" restriction to the test. Obviously it's better to prevent the output.

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/ppc64el/a/awesome/24520223/log.gz

autopkgtest [23:18:38]: test integration.sh: - - - - - - - - - - results - - - - - - - - - - integration.sh FAIL stderr: The XKEYBOARD keymap compiler (xkbcomp) reports: autopkgtest [23:18:38]: test integration.sh: - - - - - - - - - - stderr - - - - - - - - - -
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86EmojiPicker
Errors from xkbcomp are not fatal to the X server

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to