Looks like that test fails on systemd machines if libpam-systemd isn't
installed in the base system. buildds have been mangled to include
minimal^ and standard^ and glib2.0 now builds.
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Changed in: glib2.0 (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1561698
Title:
Build hangs on s390x
Status in glib2.0 package in Ubuntu:
Fix Released
Bug description:
The build reproducibly hangs on the buildds on s390x.
It's always at the same place, in the "642026" test.
https://git.gnome.org/browse/glib/tree/glib/tests/642026.c
I don't think it's this testsuite that is at fault though - the same
thing builds on other Ubuntu architectures and for Debian s390x.
The last successful build was 2.47.6-1 which used "Kernel version:
Linux z13-019 4.3.0-6-generic #17-Ubuntu SMP Mon Jan 11 21:29:24 UTC
2016 s390x"
and the latest failure was 2.47.92-1 "Kernel version: Linux z13-012
4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 s390x".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1561698/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
