maria-developers team mailing list archive

[Otto Kekäläinen <otto@xxxxxxxxx>]

Hello!

I am not sure what you mean, but the builds at
https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all
are built from the sources at https://github.com/ottok/mariadb-10.0.
Make options are visible in
https://github.com/ottok/mariadb-10.0/blob/master/debian/rules

AFAIK the tests check if TokuDB is available, and run only then. For
example on i386 the TokuDB tests are skipped automatically. I don't
know if this answered your question, but the source link is anyway
above.


2015-02-04 0:49 GMT+02:00 Peter Mclarty <peter.mclarty@xxxxxxxxxxxxxxxxxxxxxxx>:
>
> Hi Otto
>
> Ok forgive my ignorance but is Tokudb being enabled, you compile successfully but does the config enable tokudb to allow it to be tested
>
> Cheers
>
> Peter
>
> On Tue, Feb 3, 2015 at 9:08 PM, Otto Kekäläinen <otto@xxxxxxxxx> wrote:
>>
>> Hello!
>>
>> Are here any TokuDB devs who could help me debug why TokuDB does
>> repeatedly fails to pass build suite tests when built on
>> Launchpad.net?
>>
>> I repeatedly get these test failures when running MariaDB builds on
>> Launchpad: rpl-tokudb.tokudb_innodb_xa_crash tokudb_bugs.mdev4533
>> tokudb.simple_join_tokudb_innodb tokudb.truncate_txn_rollback_innodb
>> tokudb_bugs.5733_innodb
>>
>> The build run log can be viewed at
>> https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all
>> and it links to the individual build logs. All amd64 builds fail while
>> all i386 (where TokuDB is disabled) pass OK. Sounds very much like a
>> TokuDB-related issue. Or could the problem be something else and the
>> TokuDB tests are just the first victim?
>>
>>
>> Example of a recent log:
>> https://launchpadlibrarian.net/196425361/buildlog_ubuntu-vivid-amd64.mariadb-10.0_10.0.16-1~exp3~vivid1~1422913379_FAILEDTOBUILD.txt.gz
>>
>>
>> One example of the test outputs:
>>
>> ***
>> rpl-tokudb.tokudb_innodb_xa_crash 'mix,xtradb' [ fail ]
>>         Test ended at 2015-02-02 22:29:06
>>
>> CURRENT_TEST: rpl-tokudb.tokudb_innodb_xa_crash
>>
>>
>> Failed to start mysqld.1
>> mysqltest failed but provided no output
>>
>>
>>  - saving '/build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/'
>> to '/build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/'
>>  - found 'core' (1/5)
>>
>> Trying 'dbx' to get a backtrace
>>
>> Trying 'gdb' to get a backtrace
>> Compressed file
>> /build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/mysqld.1/data/core
>> ***Warnings generated in error logs during shutdown after running
>> tests: rpl-tokudb.tokudb_innodb_xa_crash
>>
>> 150202 22:29:05 [ERROR] mysqld got signal 11 ;
>> Attempting backtrace. You can use the following information to find out
>> 150202 22:29:05 [ERROR] mysqld got signal 11 ;
>> Attempting backtrace. You can use the following information to find out
>> ***