Regarding your question on differences: In MariaDB the build time and autopkg tests (part 'upstream') are running the same mtr test suite 'main'. Depending on the environment some tests might bail out, but there is no intentional difference by design.
https://launchpadlibrarian.net/407954652/buildlog_ubuntu-disco-amd64.mariadb-10.3_1%3A10.3.12-2~ubuntu19.04.1~1548328652.011399006_BUILDING.txt.gz => Completed: All 739 tests were successful. 97 tests were skipped, 42 by the test itself. https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mariadb-10.3/1892278/log.gz => Completed: All 702 tests were successful. 128 tests were skipped, 63 by the test itself. By the way, all of this is team maintained in modern Gitlab with extensive Gitlab-CI integration etc, so if you dig deeper into something and find flaws, it is very easy to fire a merge request to get it fixed: https://salsa.debian.org/mariadb-team/ Regarding mariadb-10.0: Upstream has not fixed the test suite issues and they are not that relevant, so let's keep having the test suite disabled. The mariadb-10.0 10.0.38-0+deb8u1 was uploaded to Debian Jessie almost 2 weeks ago and no regressions are reported, so it should be safe to upload this to Xenial now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814258 Title: USN-3867-1: Partially applies to MariaDB too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1814258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
