Tests connect.bin connect.endian fail on armhf (on Debian build system)

connect.bin                              [ fail ]

        Test ended at 2015-08-27 23:15:57

CURRENT_TEST: connect.bin

mysqltest: At line 28: query 'SELECT * FROM t1' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

< snip >

Warnings:

Warning	1105	Open(rb) error 2 on DATADIR/test/nonexistent.txt: No such file or directory

DROP TABLE t1;

SET time_zone='+00:00';

CREATE TABLE t1

(

fig INT(4) NOT NULL FIELD_FORMAT='C',

name CHAR(10) NOT NULL,

birth DATE NOT NULL,

id CHAR(5) NOT NULL FIELD_FORMAT='S',

salary DOUBLE(9,2) NOT NULL DEFAULT 0.00 FIELD_FORMAT='F',

dept INT(4) NOT NULL FIELD_FORMAT='S'

) ENGINE=CONNECT TABLE_TYPE=BIN BLOCK_SIZE=5 FILE_NAME='Testbal.dat' OPTION_LIST='Endian=Little';

SELECT * FROM t1;

More results from queries before failure can be found in /«PKGBUILDDIR»/builddir/mysql-test/var/log/bin.log

Server [mysqld.1 - pid: 31265, winpid: 31265, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

150827 23:15:56 [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 http://kb.askmonty.org/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.0.21-MariaDB-2-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=1

max_threads=153

thread_count=1

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61705 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0xb1bf6008

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 = 0xb6a78dc4 thread_stack 0x48000

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0xaf48b018): SELECT * FROM t1

Connection ID (thread ID): 9

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=off,table_elimination=on,extended_keys=on,exists_to_in=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

Writing a core file

----------SERVER LOG END-------------

 - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.bin/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.bin/'

 - found 'core' (0/5)

Trying 'dbx' to get a backtrace

Trying 'gdb' to get a backtrace

Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.bin/mysqld.1/data/core

***Warnings generated in error logs during shutdown after running tests: connect.alter_xml connect.alter connect.bin

150827 23:15:56 [ERROR] mysqld got signal 7 ;

Attempting backtrace. You can use the following information to find out

connect.csv                              [ pass ]     80

connect.datest                           [ pass ]      7

connect.dbf                              [ pass ]    130

connect.dir                              [ pass ]     41

connect.endian                           [ fail ]

        Test ended at 2015-08-27 23:16:06

CURRENT_TEST: connect.endian

mysqltest: At line 19: query 'SELECT * FROM t1' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

SET time_zone='+00:00';

#

# Testing little endian table

#

CREATE TABLE t1

(

fig INT(4) NOT NULL FIELD_FORMAT='C',

name CHAR(10) NOT NULL,

birth DATE NOT NULL FIELD_FORMAT='L',

id CHAR(5) NOT NULL FIELD_FORMAT='L2',

salary DOUBLE(9,2) NOT NULL DEFAULT 0.00 FIELD_FORMAT='LF',

dept INT(4) NOT NULL FIELD_FORMAT='L2'

) ENGINE=CONNECT TABLE_TYPE=BIN BLOCK_SIZE=5 FILE_NAME='Testbal.dat';

SELECT * FROM t1;

Server [mysqld.1 - pid: 31343, winpid: 31343, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

150827 23:16:06 [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 http://kb.askmonty.org/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.0.21-MariaDB-2-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=1

max_threads=153

thread_count=1

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61705 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0xb1bf6008

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 = 0xb6a4adc4 thread_stack 0x48000

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0xaf48b018): SELECT * FROM t1

Connection ID (thread ID): 19

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=off,table_elimination=on,extended_keys=on,exists_to_in=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

Writing a core file

----------SERVER LOG END-------------

 - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.endian/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.endian/'

 - found 'core' (1/5)

Trying 'dbx' to get a backtrace

Trying 'gdb' to get a backtrace

Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/connect.endian/mysqld.1/data/core

***Warnings generated in error logs during shutdown after running tests: connect.csv connect.endian connect.dbf connect.dir connect.datest

150827 23:16:06 [ERROR] mysqld got signal 7 ;

Attempting backtrace. You can use the following information to find out

connect.fix                              [ pass ]     56

connect.fmt                              [ pass ]     43

connect.general                          [ pass ]      7

connect.grant                            [ pass ]    158

connect.grant2                           [ pass ]    395

connect.index                            [ pass ]    938