The test failures were due to upstream issues, and most likely are fixed by now, so I will experiment with reverting https://salsa.debian.org/mariadb-team/mariadb-10.0/commit/62562ed38dce0bbab3bdb666f3acc01a23a33a51
I noticed a "hole" in my pipeline, the test suite is actually not forced to run anywhere, not https://salsa.debian.org/mariadb-team/mariadb-10.0/pipelines/34858, not https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all and there was no autopkgtest here either https://ci.debian.net/packages/m/mariadb-10.0/
I will address this.
By the way I don't see any MariaDB here either: http://people.canonical.com/~platform/security-britney/current/security_bionic_excuses.html
Next time you encounter issues, please report them, and give me 1-2 days time to fix, and only upload once you have fixed stuff. Anyways, I'll fix it now and they should be in place for 10.0.X upload some day.
The test failures were due to upstream issues, and most likely are fixed by now, so I will experiment with reverting https:/ /salsa. debian. org/mariadb- team/mariadb- 10.0/commit/ 62562ed38dce0bb ab3bdb666f3acc0 1a23a33a51
I noticed a "hole" in my pipeline, the test suite is actually not forced to run anywhere, not https:/ /salsa. debian. org/mariadb- team/mariadb- 10.0/pipelines/ 34858, not https:/ /launchpad. net/~mysql- ubuntu/ +archive/ ubuntu/ mariadb- 10.0/+builds? build_text= &build_ state=all and there was no autopkgtest here either https:/ /ci.debian. net/packages/ m/mariadb- 10.0/
I will address this.
By the way I don't see any MariaDB here either: http:// people. canonical. com/~platform/ security- britney/ current/ security_ bionic_ excuses. html
Next time you encounter issues, please report them, and give me 1-2 days time to fix, and only upload once you have fixed stuff. Anyways, I'll fix it now and they should be in place for 10.0.X upload some day.