[Pkg-utopia-maintainers] Bug#902209: ostree: FTBFS on s390x and ports (big-endian?): test failures: g_str_has_prefix: assertion 'str != NULL' failed

[Simon McVittie]

Source: ostree
Version: 2018.6-1
Severity: serious
Tags: ftbfs

ostree 2018.6 has test failures on s390x and some ports architectures.
s390x is a representative example:

----8<----
PASS: tests/test-repo-finder-config 1 /repo-finder-config/init
PASS: tests/test-repo-finder-config 2 /repo-finder-config/no-configs
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: g_str_has_prefix: assertion 'str != NULL' failed

# OSTree-DEBUG: ostree_repo_finder_resolve_all_async: Resolving refs [(org.example.Collection0, exampleos/x86_64/ref0), (org.example.Collection0, exampleos/x86_64/ref1), (org.example.Collection1, exampleos/x86_64/ref1), (org.example.Collection1, exampleos/x86_64/ref2), (org.example.Collection2, exampleos/x86_64/ref3)] with finders [OstreeRepoFinderConfig]
# OSTree-DEBUG: ostree_repo_finder_config_resolve_async: Checking 21474836480 remotes
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection1, exampleos/x86_64/ref2) to remote ?remote1?.
# OSTree-DEBUG: Ignoring remote ?remote1-bad-copy? due to it not advertising any of the requested refs.
# OSTree-DEBUG: Ignoring remote ?remote2? due to no valid collection ID being configured for it: Invalid collection ID (null)
Bail out! GLib-FATAL-CRITICAL: g_str_has_prefix: assertion 'str != NULL' failed
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: g_str_has_prefix: assertion 'str != NULL' failed
----8<----

----8<----
ERROR: tests/test-find-remotes.sh - too few tests run (expected 1, got 0)
ERROR: tests/test-find-remotes.sh - exited with status 133 (terminated by signal 5?)

+ env LD_PRELOAD=/<<PKGBUILDDIR>>/tests/libreaddir-rand.so ostree --repo=local find-remotes --finders=config org.example.AppsCollection app1

(ostree find-remotes:20691): GLib-CRITICAL **: 23:37:14.198: g_str_has_prefix: assertion 'str != NULL' failed
/<<PKGBUILDDIR>>/tests/test-find-remotes.sh: line 89: 20691 Trace/breakpoint trap   ${CMD_PREFIX} ostree --repo=$repo find-remotes --finders=config org.example.AppsCollection app1 > find
----8<----

I've prepared an upload to fix #902194, which will give us a better
picture of which architectures have this test failure. Right now we have:


          little-endian                         big-endian

32-bit    armel armhf i386 mipsel               mips powerpc(spe) sparc64:
          sh4 x32:                              FTBFS: #902194
          FTBFS: #902194

64-bit    amd64 arm64 mips64el ppc64el          s390x hppa ppc64:
          alpha ia64 riscv64:                   FTBFS: this bug
          successful

which looks suspiciously like correlation with big-endian architectures.
If that theory is correct, arm* i386 mipsel sh4 and x32 will succeed
after #902194 is fixed, but mips powerpc(spe) and sparc64 will continue
to FTBFS due to this bug.

    smcv