On 18/11/15 07:11, Diane Trout wrote:
> My temptation would be add the guard and and either downgrade this bug or
> file
> a new bug saying that unit tests fail on s390x. (and if you have suggestions
> on who understands dbus on s390x and could possibly answer some questions,
> I'd
> appreciat
I figured out how to log into the porter box, and tried:
running the tests with dbus-test-runner, inserting a sleep in the dbus test
start up script, and running under dbus-run-session (though possibly with test
runner still installed)
None of it helped, I kept getting 3 unit tests failures.
I
On 10/11/15 19:25, Diane Trout wrote:
> Hello,
>
> Looking through the build log it looks like its the test case that is
> failing.
> Would you happen to know if DBus behaves different on the s390x compared to
> the other architectures? (E.g. is it particularly slow?)
Not AFAIK.
Emilio
Hello,
Looking through the build log it looks like its the test case that is failing.
Would you happen to know if DBus behaves different on the s390x compared to
the other architectures? (E.g. is it particularly slow?)
Diane
Source: libaccounts-glib
Version: 1.18+20150112-1
Severity: serious
Your package failed to build on s390x. Normally this wouldn't be RC as
this package has never built on that architecture. However,
ktp-common-internals needs this (through libaccounts-qt) to build there.
Log at
https://buildd.deb
5 matches
Mail list logo
