Re: [debian-mysql] MySQL in Jessie
2014-09-01 4:03 GMT+03:00 Matthias Klose <doko@debian.org>:
..
> mysql-5.5's autopkg tests fail (this is a regression), and I didn't see any
> action to fix these. Now ignored at least in Ubuntu.
>
> mysql-5.6's autopkg tests always failed, didn't see any action to fix these.
>
> mariadb-5.5, mariadb-10.0, and percona-xtradb-cluster-server-5.5 don't have
> autopkg tests enabled at all.
>
> test results for mysql-5.x are ignored during the build for most architectures
> (there are some). didn't check for the other packages.
MariaDB does not have any autopkg tests yet, but I would be happy to
take contributions. Please note that at the moment
https://jenkins.qa.ubuntu.com/ says 'Proxy error' and the DEP-8 seems
quite unfinished (http://dep.debian.net/deps/dep8/). The documentation
at http://ci.debian.net/doc/ is though OK.
However the main test in MySQL
(http://ci.debian.net/data/packages/unstable/amd64/m/mysql-5.5/20140830_020544.autopkgtest.log)
seems to be the standard MySQL testsuite maintained by upstream.
Please note that this same testsuite is run in *every* MariaDB build
as part of standard source builds in Debian, and even if the build is
OK but testsuite fails, the whole build fails and new binaries will
not enter unstable. This does not of course account for situations
when some other dependency updates and brakes the test suite result
without any changes in the MariaDB package, but it is still pretty
good and guarantees that binaries with failing tests does not enter
Debian in the first place.
The MySQL builds also does the same thing, but at least in the log
https://buildd.debian.org/status/fetch.php?pkg=mysql-5.5&arch=s390x&ver=5.5.37-1&stamp=1398384002
it seems that the binaries are generated and enter unstable despite
the fact, that the test suite run had failures. However takes on
fixing the MySQL autopkg tests should probably fix this too.
Reply to: