[debian-mysql] Bug#920854: mariadb-10.1: FTBFS on s390x (test failure)

[Julien Cristau]

Source: mariadb-10.1
Version: 10.1.37-0+deb9u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: affects -1 + release.debian.org security.debian.org

The mariadb-10.1 package on security.d.o doesn't build on s390x, one test fails:

> CURRENT_TEST: unit.pcre_test
> 
> PCRE C library tests using test data from /<<PKGBUILDDIR>>/pcre/testdata
> PCRE version 8.42 2018-03-20
> 
> ---- Testing 8-bit library ----
> 
> Test 1: Main functionality (Compatible with Perl >= 5.10)
>   OK
>   OK with study
> Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
> Segmentation fault
>  
> ** Test 2 requires a lot of stack. If it has crashed with a
> ** segmentation fault, it may be that you do not have enough
> ** stack available by default. Please see the 'pcrestack' man
> ** page for a discussion of PCRE's stack usage.
> 
>  - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/1/log/unit.pcre_test/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/unit.pcre_test/'
> 
> Retrying test unit.pcre_test, attempt(2/3)...
> 
> unit.pcre_test                           w1 [ retry-fail ]
>         Test ended at 2018-11-15 12:08:22
> 
> CURRENT_TEST: unit.pcre_test
> 
> PCRE C library tests using test data from /<<PKGBUILDDIR>>/pcre/testdata
> PCRE version 8.42 2018-03-20
> 
> ---- Testing 8-bit library ----
> 
> Test 1: Main functionality (Compatible with Perl >= 5.10)
>   OK
>   OK with study
> Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
> Segmentation fault
>  
> ** Test 2 requires a lot of stack. If it has crashed with a
> ** segmentation fault, it may be that you do not have enough
> ** stack available by default. Please see the 'pcrestack' man
> ** page for a discussion of PCRE's stack usage.
> 
>  - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/1/log/unit.pcre_test/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/unit.pcre_test/'
> 
> Test unit.pcre_test has failed 2 times, no more retries!

Apparently such failures are somehow expected, can we disable that test if not
fix it?

Cheers,
Julien