Commit Graph

8 Commits

Author SHA1 Message Date
aeab1bdc7d Cherry-pick: Fall back to pkill in run_ctrl_c.sh
The pkill executable is provided by the same package that provides ps
which is why it is more likely to be installed. Seems that the test VMs
don't always have killall installed.

Run the MaxScale process with the maxscale user instead of the root user
to prevent any new files from being owned by a different user.

Cherry-picked the commit a06c122a5e050071589f724758d6bbd3d8d3f419 from
develop.
2020-01-13 17:12:05 +02:00
b3eb5ccc81 Fix run_ctrl_c.sh on newer systems
Systems that no longer support SysV init scripts and the service command
need to use systemctl.
2019-07-01 17:13:09 +03:00
cd732ac14f MXS-2243 System tests brings VMs by themselves (#193)
maxscale-system-test changed in order to control test environment by itself.
Every test checks which machines are running, compare with list of needed machines
and start new VMs is they are missing in the running machines list.
Tests are executiong MDBCI commands, MDBCI executable should be in the PATH
2019-04-02 13:27:34 +03:00
a2acecd229 Fix test failures
Use correct parameter name for verify_master_failure and run MaxScale
explicitly as root in run_ctrl_c.sh.
2017-12-21 10:48:06 +02:00
3c88bf1ec6 refactored tests (#147) 2017-12-08 12:23:04 +02:00
5acdfab5e6 Start MaxScale as maxscale user in run_ctrl_c.sh
MaxScale should not be started as root.
2017-11-09 14:15:47 +02:00
957b50c811 Remove trailing whitespace
Removed trailing whitespace in tests and build scripts.
2017-05-26 14:29:28 +03:00
8c6ca38a8a add tests 2017-05-23 21:09:30 +03:00