[MDEV-15303] Testsuite failure (~50 tests) on aarch64 Created: 2018-02-13  Updated: 2018-03-05  Resolved: 2018-03-05

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

Type: Bug Priority: Major
Reporter: Michal Schorm Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Fedora 26 - aarch64 only


 Description   

Hello,

With release of 10.1.31 a bigger number of tests (+- 55) started to fail.
However they do so only on aarch64.

Most of them fail with errno 2013 (lost connection during a query)

    binlog_encryption.encrypted_slave
 
    binlog_encryption.rpl_mixed_binlog_max_cache_size
 
    binlog_encryption.rpl_gtid_basic
 
    rpl.rpl_mixed_drop_create_temp_table
 
    rpl.rpl_innodb_mixed_dml
 
    rpl.rpl_mixed_drop_create_temp_table
 
    rpl.rpl_checksum_cache
 
    rpl.rpl_innodb_bug28430
 
    rpl.rpl_stm_innodb
 
    rpl.rpl_trigger
 
    rpl.rpl_deadlock_innodb
 
    rpl.rpl_commit_after_flush
 
    rpl.rpl_insert_id_pk
 
    rpl.rpl_mdev10863
 
    rpl.rpl_multi_engine
 
    rpl.rpl_slave_load_in
 
    rpl.rpl_truncate_3innodb
 
    rpl.create_select
 
    rpl.rpl_circular_for_4_hosts
 
    rpl.rpl_gtid_master_promote
 
    encryption.innodb_onlinealter_encryption
 
    encryption.innodb-read-only
 
    encryption.innodb-page_encryption_compression
 
    encryption.innodb-log-encrypt-crash
 
    encryption.innodb-redo-nokeys
 
    encryption.innodb_onlinealter_encryption
 
    encryption.innodb-read-only
 
    encryption.innodb_encryption_row_compressed
 
    encryption.innodb-checksum-algorithm
 
    encryption.innodb-encryption-alter
 
    encryption.innodb-page_encryption_compression
 
    encryption.innodb_onlinealter_encryption
 
    encryption.innodb-read-only
 
    encryption.innodb-encryption-alter
 
    encryption.innodb-page_encryption_compression
 
    encryption.innodb-redo-nokeys
 
    encryption.innodb_onlinealter_encryption
 
    encryption.innodb-read-only
 
    encryption.innodb_encryption_row_compressed
 
    encryption.innochecksum
 
    encryption.innodb-checksum-algorithm
 
    encryption.innodb-page_encryption_compression
 
    innodb.innodb-page_compression_default
 
    innodb_fts.innodb_fts_large_records
 
    innodb_fts.innodb_fts_stopword_charset
 
    innodb.innodb-page_compression_default
 
    innodb_fts.innodb_fts_large_records
 
    parts.rpl_partition

Build logs for examination:

Various info:

  • we do use backported OpenSSL 1.1 patch from 10.2. However I do not believe that should be a problem since it builds fine on all other architectures.

–

Are you aware of such issue lately?

 Comments   
Comment by Elena Stepanova [ 2018-02-14 ]

According to the log, it crashes all over the place. Possibly related to this:

<jemalloc>: Error in munmap(): Invalid argument

Comment by Daniel Black [ 2018-02-15 ]

Might be related to https://github.com/jemalloc/jemalloc/issues/467, which does have a fix in 5.0.

A cursory read suggest that jemalloc needs to be packaged on Fedora with --with-lg-page (64k) because of the default kernel page size.

Comment by Daniel Black [ 2018-02-15 ]

https://koji.fedoraproject.org/koji/rpminfo?rpmID=12811635, jemalloc-5.0.1-3.fc28.aarch64.rpm,

latest build:

https://kojipkgs.fedoraproject.org/work/tasks/7158/25047158/build.log

aarch buildlog

+ echo 'What is the pagesize?'
 
+ getconf PAGESIZE
 
4096

So jemalloc was build on a 4k page size machine. Assume the other, though I can't tell, is 64k page size.

Comment by Daniel Black [ 2018-02-15 ]

Fedora bug as per link

Comment by Daniel Black [ 2018-03-05 ]

Seem to be accepted as the issue on the RH bugzilla.

Closing as "Not our bug"

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