Bug#827473: ostree: FTBFS on mipsel: "ostree pull" sometimes gets SIGBUS, SIGSEGV

Source: ostree
Version: 2016.5-4
Severity: important
Tags: help

[X-Debbugs-Cc set to [email protected], please include them
in follow-ups.]

ostree failed to build on the mipsel buildd eberlin.debian.org:
<https://buildd.debian.org/status/fetch.php?pkg=ostree&arch=mipsel&ver=2016.5-4&stamp=1465952501>
I'm reporting this as important rather than serious because it seems
to be hard to reproduce, so I suspect a rebuild would probably be fine,
but it probably points to an underlying problem in either ostree or the
mipsel toolchain/machine.

I'm trying to reproduce this failure on the porterbox etler.debian.org
by rebuilding the package or by using the installed-tests from 2016.5-3.

One of the changes I made in 2016.5-4 was to repeat the tests 4 times
if they fail the first time, so we can see how reproducible things are.
In the failing build on eberlin, the results were:

tests/test-pull-archive-z.sh (1/5, 5/5): ostree command-line tool killed by
signal 10, which I think is SIGBUS, during "ostree pull"

tests/test-pull-large-metadata.sh (1/5): ostree command-line tool killed
by SIGBUS with no output, again during "ostree pull"

tests/test-oldstyle-partial.sh (1/5): ostree command-line tool killed
by SIGSEGV, again during "ostree pull"

tests/test-pull-metalink.sh (2/5): another SIGBUS during "ostree pull"

tests/test-pull-resume.sh (3/5, 4/5): SIGBUS during "ostree pull"

tests/test-admin-upgrade-not-backwards.sh (4/5): another SIGBUS during
"ostree pull"

tests/test-pull-depth.sh (5/5): another SIGBUS during "ostree pull"

If ostree's tests are reliable on architectures other than mipsel and
we can't reproduce the failure in an environment where stack traces are
available, I would prefer to exclude it from being built on mipsel rather
than ignore test failures, but I'm willing to be persuaded otherwise.

Any porter advice or help welcome. ostree has a standard Autotools
"make check", and GNOME-style installed-tests (mostly the same code)
wrapped in autopkgtest; if you haven't encountered those before,
the tl;dr version is that you install gnome-desktop-testing and
ostree-tests, then run "gnome-desktop-testing-runner ostree", or read
the underlying shell command-lines out of the .desktop-style files in
/usr/share/installed-tests/ostree).

Thanks,
    S