[debian-mysql] Bug#838914: mariadb-10.0: testsuite failures on mips/mipsel

Otto Kekäläinen otto at debian.org
Sat Oct 1 22:15:13 UTC 2016


Hello!

Thank you very much and well done for fixing so many test failures in one go!

I noticed however that one test started to fail om amd64 now. Builds
on i386 and ppc64 are OK. Output below and full log visible at
https://launchpadlibrarian.net/287683886/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.27-2~xenial1~1475349704.695a347_BUILDING.txt.gz

The stack trace mentions groonga - maybe you groonga/libatomic change
introduced a regression? Just an idea, I am not an expert on this.

Did you test building on amd64 with your modifications?


*******************

plugins.show_all_plugins                 w2 [ fail ]
        Test ended at 2016-10-01 20:04:21

CURRENT_TEST: plugins.show_all_plugins


The server [mysqld.1 - pid: 5113, winpid: 5113, exit: 256] crashed
while running 'check warnings'
Server log from this test:
----------SERVER LOG START-----------
161001 20:04:20 [ERROR] mysqld got signal 11 ;
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.0.27-MariaDB-2~xenial1~1475349704.695a347
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
62788 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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...
----------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
show status like '%libraries%';
Variable_name Value
Opened_plugin_libraries 2
show plugins soname like '%example%';
Name Status Type Library License
EXAMPLE NOT INSTALLED STORAGE ENGINE ha_example.so GPL
UNUSABLE NOT INSTALLED DAEMON ha_example.so GPL
daemon_example NOT INSTALLED DAEMON libdaemon_example.so GPL
three_attempts NOT INSTALLED AUTHENTICATION dialog_examples.so GPL
two_questions NOT INSTALLED AUTHENTICATION dialog_examples.so GPL
show status like '%libraries%';
Variable_name Value
Opened_plugin_libraries 6
show plugins soname where library = 'ha_example.so';
Name Status Type Library License
EXAMPLE NOT INSTALLED STORAGE ENGINE ha_example.so GPL
UNUSABLE NOT INSTALLED DAEMON ha_example.so GPL
select variable_value > 10 from information_schema.global_status where
variable_name like '%libraries%';
variable_value > 10
1



 - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/2/log/plugins.show_all_plugins/'
to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/plugins.show_all_plugins/'



More information about the pkg-mysql-maint mailing list