Merge lp:~akopytov/percona-xtrabackup/bug1250738-2.2 into lp:percona-xtrabackup/2.2
Status: | Merged |
---|---|
Approved by: | Alexey Kopytov |
Approved revision: | no longer in the source branch. |
Merged at revision: | 4901 |
Proposed branch: | lp:~akopytov/percona-xtrabackup/bug1250738-2.2 |
Merge into: | lp:percona-xtrabackup/2.2 |
Diff against target: |
153 lines (+33/-40) 6 files modified
xtrabackup/test/inc/common.sh (+16/-0) xtrabackup/test/run.sh (+10/-1) xtrabackup/test/t/bug1192347.sh (+1/-8) xtrabackup/test/t/bug983720_galerainfo.sh (+2/-10) xtrabackup/test/t/xb_galera_info.sh (+2/-10) xtrabackup/test/t/xb_galera_sst.sh (+2/-11) |
To merge this branch: | bzr merge lp:~akopytov/percona-xtrabackup/bug1250738-2.2 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexey Kopytov (community) | Approve | ||
Review via email: mp+195010@code.launchpad.net |
Description of the change
Bug #1250738: Galera tests are skipped on some Jenkins slaves with
The problem was that Galera tests checked for Galera support by starting
temporary mysqld instances without specifying a configuration file. On
some Jenkins slaves (e.g. Ubuntu ones in our cluster) there was a
default configuration file at /etc/mysql/my.cnf which had query_cache
enabled. Since query_cache is not supported by Galera, the server
refused to start, so Galera support checks in tests assumed it there is
no support and skipped the tests.
Fixed by changing the way Galera support is being detected by the test
suite. Instead of each tests having to roll its own check with a
temporary mysqld instance, run.sh performs this check on startup by
checking the wsrep_ready status variable (along with other
version-
exported to subshells, so it is available to tests. As an extra safety,
run.sh will also abort with an error, if Galera testing was explicitly
requested via -c galera55.
http://