Build log examples from the current version

*
https://buildd.debian.org/status/fetch.php?pkg=libayatana-appindicator&arch=amd64&ver=0.5.5-2&stamp=1598042050&raw=0

FAIL: test-libappindicator-fallback

*
https://buildd.debian.org/status/fetch.php?pkg=libayatana-appindicator&arch=armel&ver=0.5.5-2&stamp=1598042183&raw=0

FAIL: test-libappindicator-fallback
FAIL: test-libappindicator-status


Having failing tests and the results ignore is going to be a blocker for
Ubuntu to promote libayatana-appindicator

Hey there,

Any chance you could check on this one? That's a blocker if we want to
switch to the ayatana indicators in Ubuntu, which we should do this
cycle if we want to do it before the next LTS

Thanks,

Le 15/02/2021 à 10:48, Debian Bug Tracking System a écrit :

Hi Sebastien,

I have just uploaded a libayatana-appindicator version that should fix
this problem.

I also filed a PR upstream for this:
https://github.com/AyatanaIndicators/libayatana-appindicator/pull/19

Greets,
Mike

Hey Mike,

Great, thanks, that's helpful, I will check that next week on Ubuntu!

Cheers,
Sebastien

Le 30/04/2021 à 17:35, Mike Gabriel a écrit :

Hello,

Bug #982845 in libayatana-appindicator reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-ayatana-team/libayatana-appindicator/-/commit/0d36aa882cde48c46076cb9ac4af3e4236cc7025
------------------------------------------------------------------------
debian/rules: Fail if unit tests fail. (Closes: #982845).
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982845

We believe that the bug you reported is fixed in the latest version of
libayatana-appindicator, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 982845@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <sunweaver@debian.org> (supplier of updated libayatana-appindicator package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 30 Apr 2021 17:17:22 +0200
Source: libayatana-appindicator
Architecture: source
Version: 0.5.5-3
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers <pkg-ayatana-devel@lists.alioth.debian.org>
Changed-By: Mike Gabriel <sunweaver@debian.org>
Closes: 982845
Changes:
 libayatana-appindicator (0.5.5-3) unstable; urgency=medium
 .
   * debian/patches:
     + Add 1001_dbus-test-runner-keep-env.patch. Make sure the build HOME
       variable is propagated into dh_auto_test.
   * debian/rules:
     + Run each set of unit tests in no-parallel mode and fali if unit tests
       fail. This fixes flaky unit tests and stops ignoring those failures.
       (Closes: #982845).
     + Run gtk2/gtk3 unit tests in two different build HOME dirs.
     + No duplicate / nested dh_auto_test calls.
Checksums-Sha1:
 979c9ddc0d30c2dc2e5b6a2251320662d5df46f6 4442 libayatana-appindicator_0.5.5-3.dsc
 9010371da2a0e1f716d06ab1222b48fe4b4ad92c 16420 libayatana-appindicator_0.5.5-3.debian.tar.xz
 d15239d2dfa3e88a3dce4a945d052161a41c7999 26513 libayatana-appindicator_0.5.5-3_source.buildinfo
Checksums-Sha256:
 cc367beea7f7d1cc286d46aa1950222d3dcc8b494ba749780b19922629bbedaf 4442 libayatana-appindicator_0.5.5-3.dsc
 080eb1c339b1e77e272bd332d31824ed8231f8581cf048b74e399446ccfd896b 16420 libayatana-appindicator_0.5.5-3.debian.tar.xz
 7191dd6c59102b7699715bd0109adb39d074210cb36988bf938aef4f64369fa5 26513 libayatana-appindicator_0.5.5-3_source.buildinfo
Files:
 e439d17701a76f77f70f2ecc12eb290c 4442 libs optional libayatana-appindicator_0.5.5-3.dsc
 e6937841f075ab25a7225d8d02204572 16420 libs optional libayatana-appindicator_0.5.5-3.debian.tar.xz
 d525efad4ed740a8421c712c7e3f0d2b 26513 libs optional libayatana-appindicator_0.5.5-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmCMIkIVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx6QQQAKPbLIXZq9domD8h+eLlzMQsOBG+
N1s0bslLNfOQsf704MqmM/A0l2BvocTb6c8uN7q0+OwDG4wL87EpnvIJjcs5WLlQ
MkUifitK9uoCGCT0i7OWryF+tYMkKTROriQ62qnVQeGkoPgo4RehKXy1SH4+MhG6
hTB4GwVLfVJj0sLMre+vC6nR2y25moq+EbRqa6lQXu3lOPLpuP7eKxi3Dp+hw4te
K50h2wxsbKT7bQ+x11Xem3aoNkP82Gvri8CCOJcLQtZ00b+HdPwuRIaWcWoS5bRa
jKTY7/NJ9ixFMr73H3x4hptXIYBCwdRHkKjU9x7g4dkhWQlqgzpUXAmQYVVzM3hJ
/8kvMRSqHnFQF/3trVHO628cU+kwkZFTZBpcyz00Hz2gzWYkfzqGjpvJD9TxCByr
7ooNnZWb4MMixrNJsSx/pQOGbH1UB9HZWSO8wWCCmZP7o166KBviOlPqB3W9G602
so0qLZvFrvVP2+RjFCEwfyvkXKoiqY5rAOe87BCyW/R17vu2lj0kf9vanqJeByuH
qd0RW9WQ3oLfcjJdiWVRWDyY0A7iugm+MFPaa9E8ZHXGuUzPQvEGgvBD07cbwDVt
wfJ9zUqCnFDR8/azwXc3zDwvD0zhfCqPPacDp5HiJqHCUs2qht5oY//2+LIi50wm
x8H7NIxvdDF8n0c8
=BjtY
-----END PGP SIGNATURE-----

Hi Sebastien,

The Debian builds failed for two architectures [1,2], and also with
the upstream DEBs I see test failures regularly, even if all unit
testing is done in absolutely non-parallel mode.

Will need to reinvestigate. I am on it.

Mike

[1]
https://buildd.debian.org/status/fetch.php?pkg=libayatana-appindicator&arch=powerpc&ver=0.5.5-3&stamp=1619798940&raw=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=libayatana-appindicator&arch=ppc64&ver=0.5.5-3&stamp=1619798973&raw=0