On 12/14/2015 04:08 PM, Dimitri John Ledkov wrote:
> Cool, thanks. Looking at build logs it seems to fail in the testsuite =(
> Does the test potentially depends on accounts to be available and installed already?
Nope.
> https://launchpadlibrarian.net/229437977/buildlog_ubuntu-xenial-s390x
> .libaccounts-glib_1.19%2B16.04.20151209.2-0ubuntu1_BUILDING.txt.gz
>
> has:
>
> task-0: ** (process:58186): DEBUG: Error message:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> com.google.code.AccountsSSO.Accounts.Manager was not provided by any
> .service files
This is always printed, the errors are others. I actually got another
report about libaccounts-glib tests failing for s390x in Debian, with a
similar error log.
Is there something special about the s390x architecture that could cause
us misbehaving? Things like endiannes, pointer size, etc. that are
different from the other architectures?
Do you know if SQLite and D-Bus work fine under s390x?
On 12/14/2015 04:08 PM, Dimitri John Ledkov wrote:
> Cool, thanks. Looking at build logs it seems to fail in the testsuite =(
> Does the test potentially depends on accounts to be available and installed already?
Nope.
> https:/ /launchpadlibra rian.net/ 229437977/ buildlog_ ubuntu- xenial- s390x glib_1. 19%2B16. 04.20151209. 2-0ubuntu1_ BUILDING. txt.gz org.freedesktop .DBus.Error. ServiceUnknown: The name code.AccountsSS O.Accounts. Manager was not provided by any
> .libaccounts-
>
> has:
>
> task-0: ** (process:58186): DEBUG: Error message:
> GDBus.Error:
> com.google.
> .service files
This is always printed, the errors are others. I actually got another
report about libaccounts-glib tests failing for s390x in Debian, with a
similar error log.
Is there something special about the s390x architecture that could cause
us misbehaving? Things like endiannes, pointer size, etc. that are
different from the other architectures?
Do you know if SQLite and D-Bus work fine under s390x?