It was discovered, that MariaDB 10.0 builds done by official Ubuntu infrastructure on Launchpad randomly has failures in TokuDB tests:
Example of one failure:
See recent log at https://launchpadlibrarian.net/252003566/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.24-5ubuntu2_BUILDING.txt.gz
Overview of mariadb-10.0 builds on their way into the Ubuntu 16.04 repository: https://launchpad.net/ubuntu/+source/mariadb-10.0/+publishinghistory
This test failure leads to the whole build exiting as unsuccessful, which in turn stops the new MariaDB package revision to enter the Ubuntu 16.04 archive.
The issue is hard to reproduce. I've seen it a few times in our own MariaDB test PPA, e.g
I just triggered multiple builds in a row but they are all successful.
I have not seen this issue surface on official Debian build systems.
I managed though to reproduce this partially in my own build system in a xenial environment: http://labs.seravo.fi/~otto/debian/mariadb-10.0-xenial-amd64/mariadb-10.0_10.0.24-5_amd64.build-d7c9399-pbuilder.log Interestingly though the test suite does not exit properly despite failing TokuDB tests and the build ends up being successful.
I have no idea how to proceed with this. Please somebody pick this up.