Bug#994741: regression tests: skipped vs failed

[<ian_bruce@mail.ru>]

On Tue, 21 Sep 2021 12:33:07 +0300
Andrius Merkys <merkys@debian.org> wrote:

> if(${CMAKE_SIZEOF_VOID_P} EQUAL 8)
>      set(RENDERING_TESTS_64bit
>          # .otf font with compressed SVG glyphs
>          # (test not stable on 32bit Windows)
>          text-gzipped-svg-glyph
>      )
> endif()
> 
> Thus this test is only run on 64bit architectures.

Thanks for pointing that out.

It appears that my assumption that this regression test failure was the
cause of the overall build failure on amd64, was incorrect. According to
the build logs, this test also fails on ppc64 and sparc64, and yet the
builds for those architectures have apparently succeeded.

This appears to be the critical failure on amd64:


    cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu && /usr/bin/ctest --force-new-ctest-process
    ninja: build stopped: subcommand failed.
    dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 ninja test returned exit code 1
    make[1]: *** [debian/rules:21: override_dh_auto_test-arch] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:8: binary-arch] Error 2
    dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
    --------------------------------------------------------------------------------
    Build finished at 2021-08-21T15:19:37Z


Since the regression test failure is apparently an unrelated problem,
how should that be interpreted?