leap_platform.git/tests/server-tests, branch clean_vcsrepo [leap_platform] tests: check process by either process scan or service name. closes #8753 2017-02-10T00:34:56+00:00 elijah elijah@riseup.net 2017-02-10T00:34:56+00:00 9e68982b4ef8af087e8792e502d37632d1a9a0e8 






New unbound runs with debug flag by default
2017-01-10T18:43:30+00:00

varac
varacanero@zeromail.org

2017-01-10T18:43:30+00:00

9b8314f3d2707a80e6238bb173280de291ecd2f4












bugfix: remove deprecated parameter from soledad test script
2016-12-23T14:07:37+00:00

drebs
drebs@riseup.net

2016-12-22T22:23:21+00:00

889e206ac2dfab93adbc3ad70ab0ba4f883de2e2












Change regex for soledad process check
2016-12-23T12:03:48+00:00

varac
varacanero@zeromail.org

2016-12-23T12:03:33+00:00

6814e226d90944b4adde33ad4946ff7a400b413e












Merge branch 'bug/avoid-hanging-soledad-sync-test-scripts' into 'master'

2016-11-24T17:54:36+00:00

Varac
varac@leap.se

2016-11-24T17:54:36+00:00

48517a1c654800db47239f4a8599d91f2c909833


Bug/avoid hanging soledad sync test scripts

See merge request !53





Bug/avoid hanging soledad sync test scripts

See merge request !53






use lock to avoid running multiple soledad tests (#8590)
2016-11-22T14:57:22+00:00

drebs
drebs@riseup.net

2016-11-18T20:16:41+00:00

389228df6ee52ce41cc83c2b91fe0b6572d4bc50

If a soledad sync test script is already running, there's no need to run
another one. This avoids having multiple test script hanging and eating
up resources.

We have seen this situation under development circumstances, when the
soledad server has been modified in a way that the client hangs and
never finishes.





If a soledad sync test script is already running, there's no need to run
another one. This avoids having multiple test script hanging and eating
up resources.

We have seen this situation under development circumstances, when the
soledad server has been modified in a way that the client hangs and
never finishes.







add a timeout for the soledad sync test script (#8590)
2016-11-22T14:57:16+00:00

drebs
drebs@riseup.net

2016-11-18T20:03:26+00:00

678a211ca31a7801d8bef8a74ca30feaa16af508

If for any reason a sync takes too long, the script will timeout and log
an errro.





If for any reason a sync takes too long, the script will timeout and log
an errro.







Don't do strict checking for nickserver
2016-11-09T12:50:30+00:00

varac
varacanero@zeromail.org

2016-11-09T12:50:30+00:00

d8255eb07a8b96ad04fcade8486530db2e61dad4

Sometimes nickserver is listed with `ruby /usr/bin/nickserver start`
in the process table, sometimes with `/usr/bin/ruby /usr/bin/nickserver start`.

We should do proper checking with `systemctl status nickserver` to make
sure the service is up though (https://leap.se/code/issues/8579).

Meanwhile it's ok to not do strict checking.





Sometimes nickserver is listed with `ruby /usr/bin/nickserver start`
in the process table, sometimes with `/usr/bin/ruby /usr/bin/nickserver start`.

We should do proper checking with `systemctl status nickserver` to make
sure the service is up though (https://leap.se/code/issues/8579).

Meanwhile it's ok to not do strict checking.







New nickserver is using fully qualified ruby path now
2016-11-08T20:05:39+00:00

varac
varacanero@zeromail.org

2016-11-08T20:05:39+00:00

4d8a1bc0ce304404e4d0cab0ce6a3c51ed035e71












Fix Are_daemons_running test for nickserver
2016-10-18T19:26:25+00:00

varac
varacanero@zeromail.org

2016-10-18T19:26:25+00:00

d834b1de3c90ed1f5416ba637e2d5d5c8e81acd5