Daniel Black added a comment - 2021-09-06 04:39 All encompassing bug reports aren't useful. The range of issues here are different s390x isn't 32 fixing a few things per - MDEV-26109 armhf isn't going to be supported unless there's a user demand. Like MDEV-24756 distros picking up architectures because they build and pass most tests generally reflects badly on MariaDB when things do fail. CONC-268 covers some unit.conc_connection

Otto Kekäläinen added a comment - 2020-10-12 10:49 Also uploaded to https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.5/+builds?build_text=&build_state=all a build version for testing different archs. Results below s390x ppc64el armhf arm64 amd64 disks.disks w2 [ fail ] Test ended at 2020-10-11 23:42:10   CURRENT_TEST: disks.disks --- /<<PKGBUILDDIR>>/plugin/disks/mysql-test/disks/disks.result 2020-08-07 12:57:37.000000000 +0000 +++ /<<PKGBUILDDIR>>/plugin/disks/mysql-test/disks/disks.reject 2020-10-11 23:42:10.002711946 +0000 @@ -9,4 +9,4 @@ ) ENGINE=MEMORY DEFAULT CHARSET=utf8 select sum(Total) > sum(Available), sum(Total)>sum(Used) from information_schema.disks; sum(Total) > sum(Available) sum(Total)>sum(Used) -1 1 +NULL NULL s390x ppc64el armhf arm64 amd64 type_test.type_test_double w4 [ fail ] Test ended at 2020-10-11 23:42:11   CURRENT_TEST: type_test.type_test_double --- /<<PKGBUILDDIR>>/plugin/type_test/mysql-test/type_test/type_test_double.result 2020-08-07 12:57:37.000000000 +0000 +++ /<<PKGBUILDDIR>>/plugin/type_test/mysql-test/type_test/type_test_double.reject 2020-10-11 23:42:11.792711946 +0000 @@ -290,7 +290,7 @@ CHARACTER_MAXIMUM_LENGTH NULL CHARACTER_OCTET_LENGTH NULL NUMERIC_PRECISION 22 -NUMERIC_SCALE 31 +NUMERIC_SCALE NULL DATETIME_PRECISION NULL CHARACTER_SET_NAME NULL COLLATION_NAME NULL s390x perfschema.memory_aggregate_32bit w4 [ fail ] Test ended at 2020-10-11 23:42:15   CURRENT_TEST: perfschema.memory_aggregate_32bit --- /<<PKGBUILDDIR>>/mysql-test/suite/perfschema/r/memory_aggregate_32bit.result 2020-08-07 12:57:36.000000000 +0000 +++ /<<PKGBUILDDIR>>/mysql-test/suite/perfschema/r/memory_aggregate_32bit.reject 2020-10-11 23:42:14.882711946 +0000 @@ -257,14 +257,14 @@ EVENT_NAME memory/sql/User_level_lock COUNT_ALLOC 2 COUNT_FREE 1 -SUM_NUMBER_OF_BYTES_ALLOC 200 -SUM_NUMBER_OF_BYTES_FREE 8 +SUM_NUMBER_OF_BYTES_ALLOC 272 +SUM_NUMBER_OF_BYTES_FREE 16 LOW_COUNT_USED 0 CURRENT_COUNT_USED 1 HIGH_COUNT_USED 2 LOW_NUMBER_OF_BYTES_USED 0 -CURRENT_NUMBER_OF_BYTES_USED 192 -HIGH_NUMBER_OF_BYTES_USED 200 +CURRENT_NUMBER_OF_BYTES_USED 256 +HIGH_NUMBER_OF_BYTES_USED 272 username user1 EVENT_NAME memory/sql/user_var_entry::value COUNT_ALLOC 3 @@ -289,14 +289,14 @@ EVENT_NAME memory/sql/User_level_lock COUNT_ALLOC 2 COUNT_FREE 1 -SUM_NUMBER_OF_BYTES_ALLOC 200 -SUM_NUMBER_OF_BYTES_FREE 8 +SUM_NUMBER_OF_BYTES_ALLOC 272 +SUM_NUMBER_OF_BYTES_FREE 16 LOW_COUNT_USED 0 CURRENT_COUNT_USED 1 HIGH_COUNT_USED 2 LOW_NUMBER_OF_BYTES_USED 0 -CURRENT_NUMBER_OF_BYTES_USED 192 -HIGH_NUMBER_OF_BYTES_USED 200 +CURRENT_NUMBER_OF_BYTES_USED 256 +HIGH_NUMBER_OF_BYTES_USED 272 USER user1 HOST localhost EVENT_NAME memory/sql/user_var_entry::value @@ -315,14 +315,14 @@ (..continues..) s390x ppc64el armhf arm64 amd64 unit.conc_connection w2 [ fail ] Test ended at 2020-10-11 23:44:20   CURRENT_TEST: unit.conc_connection # port: 16020 # socketname: /<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/2/mysqld.1.sock 1..34 # Testing against MySQL Server 10.5.5-MariaDB-4~ubuntu20.10.1~1602458170.84f9c0e86.ma # Host: Localhost via UNIX socket # Client library: 10.5.5 ok 1 - test_default_auth ok 2 - test_conc443 # client_ed25519 plugin not available ok 3 # skip test_conc366 ok 4 - test_conc392 # caching_sha256_password not supported ok 5 # skip test_conc312 ok 6 - test_conc351 # server_status: 16386 # server_status after changing autocommit: 16384 # server_status after mysql_change_user: 16386 ok 7 - test_conc332 ok 8 - test_conc327 ok 9 - test_conc317 # csname=utf8mb4 ok 10 - test_conc315 # Server doesn't support password expiration ok 11 # skip test_expired_pw # Cipher in use: DHE-RSA-AES256-SHA # Cipher in use: DHE-RSA-AES256-SHA ok 12 - test_conc276 # character set: latin2 ok 13 - test_mdev13100 # sha256_password plugin not available ok 14 # skip test_auth256 ok 15 - test_reset ok 16 - test_unix_socket_close # session tracking not fully supported yet in 10.2 ok 17 # skip test_sess_track_db # foo1 => bar1 # foo3 => bar3 # foo2 => bar2 ok 18 - test_get_options # test doesn't work with unix sockets ok 19 # skip test_wrong_bind_address # test doesn't work with unix sockets ok 20 # skip test_bind_address ok 21 - test_conc118 # user: conc66 ok 22 - test_conc66 ok 23 - test_bug20023 # Due to mysql_change_user security fix this test will not work anymore. ok 24 # skip test_bug31669 # error: Can't connect twice. Already connected ok 25 - test_bug33831 # Due to mysql_change_user security fix this test will not work anymore. ok 26 # skip test_change_user true: 1 ok 27 - test_opt_reconnect ok 28 - test_compress # Thread_id before kill: 3602 # Thread_id after kill: 3603 ok 29 - test_reconnect # Error: String server version mismatch (/<<PKGBUILDDIR>>/libmariadb/unittest/libmariadb/connection.c: 624) not ok 30 - test_conc21 # error: Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) # error: Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) ok 31 - test_conc26 # error: Can't connect to MySQL server on '192.168.1.101' (110) # elapsed: 5 ok 32 - test_connection_timeout # error: Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) # elapsed: 0 ok 33 - test_connection_timeout2 # error: Lost connection to MySQL server during query # elapsed: 5 # elapsed: 10 ok 34 - test_connection_timeout3 # close default # Failed 1 tests! armhf compat/oracle.sp-package w4 [ fail ] Test ended at 2020-10-12 00:52:26   CURRENT_TEST: compat/oracle.sp-package mysqltest: At line 2230: query 'SELECT p1.f1()' failed: 2013: Lost connection to MySQL server during query   The result from queries just before the failure was: < snip > DROP PACKAGE p1; DROP TABLE t1; # # Package variables and XPath # CREATE PACKAGE p1 AS FUNCTION f1 RETURN TEXT; END; $$ CREATE PACKAGE BODY p1 AS i INT:=0; xml TEXT:= '<a><b>b1</b><b>b2</b><b>b3</b></a>'; FUNCTION f1 RETURN TEXT AS BEGIN SET i=i+1; RETURN ExtractValue(xml, '/a/b[$i]'); END; END; $$ SELECT p1.f1();   More results from queries before failure can be found in /<<PKGBUILDDIR>>/builddir/mysql-test/var/4/log/sp-package.log     Server [mysqld.1 - pid: 9021, winpid: 9021, exit: 256] failed during test run Server log from this test: ----------SERVER LOG START----------- 201012 0:52:24 [ERROR] mysqld got signal 7 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware.   To report this bug, see https://mariadb.com/kb/en/reporting-bugs   We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.   Server version: 10.5.5-MariaDB-4~ubuntu20.10.1~1602458170.84f9c0e86.master. key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=2 max_threads=153 thread_count=3 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62243 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 0xf22006b8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0xf2468c44 thread_stack 0x49000   Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0xf220d998): SELECT p1.f1() Connection ID (thread ID): 152 Status: NOT_KILLED   Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off   The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /<<PKGBUILDDIR>>/builddir/mysql-test/var/4/mysqld.1/data Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 31809 31809 processes Max open files 1024 1024 files Max locked memory 16777216 16777216 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 31809 31809 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: |/usr/share/apport/apport %p %s %c %d %P %E   ----------SERVER LOG END------------- s390x period.overlaps 'innodb' w1 [ fail ] Test ended at 2020-10-12 07:59:17   CURRENT_TEST: period.overlaps --- /<<PKGBUILDDIR>>/mysql-test/suite/period/r/overlaps.result 2020-08-07 12:57:36.000000000 +0000 +++ /<<PKGBUILDDIR>>/mysql-test/suite/period/r/overlaps.reject 2020-10-12 07:59:17.451925794 +0000 @@ -127,7 +127,7 @@ create or replace table t(id int, s date, e date, period for p(s,e), primary key(id, s, p without overlaps)); -ERROR HY000: Key `(null)` cannot explicitly include column `s` +ERROR HY000: Key `(null)` cannot explicitly include column `` create or replace table t(id int, s date, e date, period for p(s,e), primary key(id)); armhf versioning.partition 'innodb,timestamp' w4 [ fail ] Test ended at 2020-10-12 09:22:03   CURRENT_TEST: versioning.partition mysqltest: At line 319: query 'create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current )' failed: 4127: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL'   The result from queries just before the failure was: < snip > explain partitions select * from t1 for system_time as of '2001-02-04 10:20:30'; id select_type table partitions type possible_keys key key_len ref rows Extra 1 SIMPLE t1 p0_p0sp0,p0_p0sp1,p2_p2sp0,p2_p2sp1,pn_pnsp0,pn_pnsp1 ALL NULL NULL NULL NULL # Using where set @ts=(select row_end from t1 for system_time all where i=1); select * from t1 for system_time all where row_end = @ts; i 1 explain partitions select * from t1 for system_time all where row_end = @ts; id select_type table partitions type possible_keys key key_len ref rows Extra 1 SIMPLE t1 p1_p1sp0,p1_p1sp1 # NULL NULL NULL NULL # # # # MDEV-16023 Unfortunate error message WARN_VERS_PART_FULL # set timestamp= unix_timestamp('2020-07-29 10:30:10'); create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current );   More results from queries before failure can be found in /<<PKGBUILDDIR>>/builddir/mysql-test/var/4/log/partition.log   - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/4/log/versioning.partition-innodb,timestamp/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/versioning.partition-innodb,timestamp/'   Retrying test versioning.partition, attempt(2/3)...   ***Warnings generated in error logs during shutdown after running tests: versioning.partition   2020-10-12 9:22:01 0 [Warning] Plugin 'test_versioning' is of maturity level experimental while the server is stable 2020-10-12 9:22:03 4 [Warning] mariadbd: Versioned table `test`.`t1`: last HISTORY partition (`p1`) is out of LIMIT, need more HISTORY partitions 2020-10-12 9:22:03 4 [Warning] mariadbd: Versioned table `test`.`t1`: last HISTORY partition (`p1`) is out of LIMIT, need more HISTORY partitions s390x period.overlaps 'myisam' w1 [ fail ] Test ended at 2020-10-12 07:59:30   CURRENT_TEST: period.overlaps --- /<<PKGBUILDDIR>>/mysql-test/suite/period/r/overlaps.result 2020-08-07 12:57:36.000000000 +0000 +++ /<<PKGBUILDDIR>>/mysql-test/suite/period/r/overlaps.reject 2020-10-12 07:59:30.161905772 +0000 @@ -127,7 +127,7 @@ create or replace table t(id int, s date, e date, period for p(s,e), primary key(id, s, p without overlaps)); -ERROR HY000: Key `(null)` cannot explicitly include column `s` +ERROR HY000: Key `(null)` cannot explicitly include column `` create or replace table t(id int, s date, e date, period for p(s,e), primary key(id)); armhf versioning.partition 'innodb,trx_id' w4 [ fail ] Test ended at 2020-10-12 09:22:08   CURRENT_TEST: versioning.partition mysqltest: At line 319: query 'create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current )' failed: 4127: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL'   The result from queries just before the failure was: < snip > explain partitions select * from t1 for system_time as of '2001-02-04 10:20:30'; id select_type table partitions type possible_keys key key_len ref rows Extra 1 SIMPLE t1 p0_p0sp0,p0_p0sp1,p2_p2sp0,p2_p2sp1,pn_pnsp0,pn_pnsp1 ALL NULL NULL NULL NULL # Using where set @ts=(select row_end from t1 for system_time all where i=1); select * from t1 for system_time all where row_end = @ts; i 1 explain partitions select * from t1 for system_time all where row_end = @ts; id select_type table partitions type possible_keys key key_len ref rows Extra 1 SIMPLE t1 p1_p1sp0,p1_p1sp1 # NULL NULL NULL NULL # # # # MDEV-16023 Unfortunate error message WARN_VERS_PART_FULL # set timestamp= unix_timestamp('2020-07-29 10:30:10'); create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current );   More results from queries before failure can be found in /<<PKGBUILDDIR>>/builddir/mysql-test/var/4/log/partition.log   - saving '/<<PKGBUILDDIR>>/builddir/mysql-test/var/4/log/versioning.partition-innodb,trx_id/' to '/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/versioning.partition-innodb,trx_id/'   Retrying test versioning.partition, attempt(2/3)...   ***Warnings generated in error logs during shutdown after running tests: versioning.partition   2020-10-12 9:22:06 0 [Warning] Plugin 'test_versioning' is of maturity level experimental while the server is stable 2020-10-12 9:22:07 4 [Warning] mariadbd: Versioned table `test`.`t1`: last HISTORY partition (`p1`) is out of LIMIT, need more HISTORY partitions 2020-10-12 9:22:07 4 [Warning] mariadbd: Versioned table `test`.`t1`: last HISTORY partition (`p1`) is out of LIMIT, need more HISTORY partitions   versioning.partition 'heap,innodb' w1 [ fail ] Test ended at 2020-10-12 09:22:12   CURRENT_TEST: versioning.partition mysqltest: At line 319: query 'create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current )' failed: 4127: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL'   versioning.partition 'innodb,traditional' w2 [ fail ] Test ended at 2020-10-12 09:22:16   CURRENT_TEST: versioning.partition mysqltest: At line 319: query 'create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current )' failed: 4127: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL'   versioning.partition 'innodb,myisam' w1 [ fail ] Test ended at 2020-10-12 09:22:19   CURRENT_TEST: versioning.partition mysqltest: At line 319: query 'create or replace table t1 (a int) with system versioning partition by system_time interval 1 second ( partition p0 history, partition p1 history, partition pc current )' failed: 4127: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL' s390x ppc64el armhf arm64 amd64 disks.disks_notembedded w3 [ fail ] Test ended at 2020-10-12 08:12:49   CURRENT_TEST: disks.disks_notembedded --- /<<PKGBUILDDIR>>/plugin/disks/mysql-test/disks/disks_notembedded.result 2020-08-07 12:57:37.000000000 +0000 +++ /<<PKGBUILDDIR>>/plugin/disks/mysql-test/disks/disks_notembedded.reject 2020-10-12 08:12:49.461862814 +0000 @@ -16,7 +16,7 @@ connection con1; select sum(Total) > sum(Available), sum(Total)>sum(Used) from information_schema.disks; sum(Total) > sum(Available) sum(Total)>sum(Used) -1 1 +NULL NULL connection default; DROP USER user1@localhost; # End of 10.1 tests

Otto Kekäläinen added a comment - 2020-10-12 10:27 Note that the above failures happened when I ran mtr as root. When I ran it as a regular user, all 4443 tests completed without issues. It does not make sense to my why, but apparently it is so.