← Back to team overview

maria-discuss team mailing list archive

Re: Test failures in my build of MariaDB 10.5.4

 

Hi, Chris!

On Aug 06, Chris Ross (cross2) wrote:
> Thanks Sergei.  Attached is a trimmed version of the var/stdout.log from
> the recent mtr run.  Let me know if there is other ancillary data for 
> any of these tests that I can also provide.
> 
> - Chris

> Checking supported features...
> MariaDB Version 10.5.4-MariaDB-debug
>  - SSL connections supported
>  - binaries are debug compiled
> Using suites: main-,archive-,binlog-,binlog_encryption-,client-,csv-,compat/oracle-,compat/mssql-,encryption-,federated-,funcs_1-,funcs_2-,gcol-,handler-,heap-,innodb-,innodb_fts-,innodb_gis-,innodb_i_s-,innodb_zip-,json-,maria-,mariabackup-,multi_source-,optimizer_unfixed_bugs-,parts-,perfschema-,plugins-,roles-,rpl-,stress-,sys_vars-,sql_sequence-,unit-,vcol-,versioning-,period-,sequence,sql_discovery,disks,metadata_lock_info,query_response_time,type_inet,user_variables
> Collecting tests...
> Installing system database...
> worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
> 
> ==============================================================================
> 
> TEST                                      RESULT   TIME (ms) or COMMENT
> --------------------------------------------------------------------------
> 
> csv.read_only                            [ fail ]
>         Test ended at 2020-08-06 03:50:10
> 
> CURRENT_TEST: csv.read_only
> --- /Volume/home/admin/mariadb-10.5.4/mysql-test/suite/csv/read_only.result	2020-06-23 15:10:16.000000000 +0000
> +++ /Volume/home/admin/mariadb-10.5.4/mysql-test/suite/csv/read_only.reject	2020-08-06 03:50:10.317359127 +0000
> @@ -6,27 +6,23 @@
>  TABLE_SCHEMA	test
>  TABLE_NAME	t1
>  TABLE_TYPE	BASE TABLE
> -ENGINE	NULL
> -VERSION	NULL
> -ROW_FORMAT	NULL
> -TABLE_ROWS	NULL
> -AVG_ROW_LENGTH	NULL
> -DATA_LENGTH	NULL
> -MAX_DATA_LENGTH	NULL
> -INDEX_LENGTH	NULL
> -DATA_FREE	NULL
> +ENGINE	CSV
> +VERSION	10
> +ROW_FORMAT	Fixed
> +TABLE_ROWS	2
> +AVG_ROW_LENGTH	0
> +DATA_LENGTH	0
> +MAX_DATA_LENGTH	0
> +INDEX_LENGTH	0
> +DATA_FREE	0

This test is doing

  chmod 0400 $datadir/test/t1.CSM;
  chmod 0400 $datadir/test/t1.CSV;

and then tries to open the table (in RW mode).
Normally this should fail, but not in your case. Are you using
a filesystem that doesn't enforce file permissions?

> main.fix_priv_tables                     [ pass ]    452
> main.flush_logs_not_windows              [ fail ]
>         Test ended at 2020-08-06 03:52:29
> 
> CURRENT_TEST: main.flush_logs_not_windows
> mysqltest: At line 10: query 'flush logs' succeeded - should have failed with errno 1004...

same here. chmod u-w and and attempt to write.

> The result from queries just before the failure was:
> flush logs;
> 
>  - saving '/Volume/home/admin/mariadb-10.5.4/mysql-test/var/log/main.flush_logs_not_windows/' to '/Volume/home/admin/mariadb-10.5.4/mysql-test/var/log/main.flush_logs_not_windows/'
> main.flush_table                         [ pass ]   4057
> 
> [ ... ]
> 
> main.mysql_tzinfo_to_sql_symlink         [ pass ]     45
> main.mysqld--help 'unix'                 [ fail ]
>         Test ended at 2020-08-06 03:54:43
> 
> CURRENT_TEST: main.mysqld--help
> --- /Volume/home/admin/mariadb-10.5.4/mysql-test/main/mysqld--help.result	2020-06-23 15:10:16.000000000 +0000
> +++ /Volume/home/admin/mariadb-10.5.4/mysql-test/main/mysqld--help.reject	2020-08-06 03:54:43.067329670 +0000
> @@ -1797,10 +1797,10 @@
>  sync-relay-log-info 10000
>  sysdate-is-now FALSE
>  system-versioning-alter-history ERROR
> -table-cache 421
> +table-cache 2000
>  table-definition-cache 400
> -table-open-cache 421
> -table-open-cache-instances 1
> +table-open-cache 2000
> +table-open-cache-instances 8

this happens if setrlimit(RLIMIT_NOFILE) fails to set the limit.

>  tc-heuristic-recover OFF
>  tcp-keepalive-interval 0
>  tcp-keepalive-probes 0
> 
> mysqltest: Result length mismatch

I didn't look further, the environment looks sufficiently non-standard
already. These tests, above, they are skipped on Windown and when run as
a root user. But, apparently, it's not enough to cover your case.
We can add more precondition checks to skip these tests as needed, but
you'll have to tell us what those precondition checks should be :)

Regards,
Sergei
VP of MariaDB Server Engineering
and security@xxxxxxxxxxx


References