Bug#804567: libaccounts-glib: FTBFS on s390x
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 was tempted to just wrap the test runner in a guard condition to avoid
running tests on s390x, since they run everywhere else.
On one hand that seems like cheating, but on the other I'm not sure anyone is
going to run a desktop on s390x.
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
appreciate it)
What do you think?
Reply to: