[MDEV-17865] unit.pcre_test fails on s390 in Debian Stretch Created: 2018-11-28  Updated: 2021-09-06  Resolved: 2021-09-06

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 10.1.37
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Vicențiu Ciorbaru Assignee: Daniel Black
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

unit.pcre_test                           w1 [ fail ]
        Test ended at 2018-11-15 12:08:21
 
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!



 Comments   
Comment by Otto Kekäläinen [ 2018-11-29 ]

Note this failure has been seen only on Debian Stretch (via security upload, build log not public). On latest Debian unstable s390x builds fine. See logs at https://buildd.debian.org/status/package.php?p=mariadb-10.1

Comment by Otto Kekäläinen [ 2020-10-11 ]

I removed the skiplists for these tests in https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/bde2cf481fa48a0dd85b9ad40e27ad5005ad1122 as we nowadays only run the main test suite as part of the builds (see debian/rules).

Comment by Otto Kekäläinen [ 2020-10-12 ]

I uploaded to Launchpad a version with the extended testing enabled. Seem the unit.pcre_test did not run at all, so I don't know what the status of this is now.

https://launchpadlibrarian.net/501650715/buildlog_ubuntu-groovy-s390x.mariadb-10.5_1%3A10.5.5-4~ubuntu20.10.1~1602458170.84f9c0e86.master.next_BUILDING.txt.gz

Comment by Otto Kekäläinen [ 2020-10-12 ]

Seems the whole test file is gone?

https://github.com/MariaDB/server/search?q=pcre_test&type=code

Comment by Daniel Black [ 2021-09-06 ]

The test was part of pcre/RunTest that is removed in 10.5. The bundled version in <10.5 has since been bumped to 8.45

The bundled pcre and tests are only used per criteria in cmake/pcre.cmake, explicit WITH_PCRE:STRING=bundled HAVE_PCRE_STACK_GUARD!=1 or PCRE_STACK_SIZE_OK!=1.

Per the buildlog above pcre2 (aka 10.X+) is used and not the bundled version.

Even if the bundled pcre was used, its an upstream bug. And upstream is effectively closed on the pcre-8 series. So closing

With bugs like MDEV-26110, s390x probably isn't safe on <10.5

Generated at Thu Feb 08 08:39:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.