* wait for procdump to exit too.
* move running process check up, propagate status. First check whether processes are still running before attempting to force kill them
* only list processes, don't change their state
* add stopping procdump in all places
* Bug fix/update foxx services after restore (#6774)
* triggers foxx queue update which leads to the internal selfHeal function of a foxx app to make foxx apps publicy visible after a foxx app is restored
* this will also add the recognition of imported foxx services
* Testing JS refactoring
* Added test case for Foxx dump -> restore cases
* Fixed check, sth- i tries to contact to the foxx service. Test is red now.
* Fixed tests for dump / restore using Foxx. Also first draft to fix the fox side. Blocked by sth. fixed in the Main Repositorx already
* Fixed typo in dump/restore testsuite
* Removed old version of the fix
* Fixed JSLint
* Removed debug-log output from foxx manager
- make sure we only check exactly _once_ for the exit status of a server
that is no longer running
- don't do a separate loop about Coordinator/DB-Server shutdown
- output the instance type after naming it being shut down
- as before, shut down DBserver and Coordinators first, then the agency.
* Re-Add the now optional method to automatically analyze crashes
* the user or CI may now specify `--coreCheck true` if the testsuite
should perform automatic core analysis for him.
* improve english, fix object member to address as pointed out by @dan
- migrate the process handling to c++ where appropriate
- move code definition / usage closer together
- add function to portably detect external processes (not spawned by us) and whether we may
- send them signals
- add portable code to send signals to processes
- for linux match what impact a signal will have on the process we send it
- check the status of the process we sent the signal, and return if its non-deadly or the process terminated
- after 8 retries with 1 second sleep send a hard kill.
- killExternal() now returns the same structure as statusExternal()
- don't block signals on spawned processes
* If our arango-object claims its got a connection to the arangodb server, use it to send a shutdown signal to the server.
If not, fall back to using a download http request.
* don't use kill to shut down the server, we now can use the regular shutdown command.
* Cleanup after each testrun
- add a success testsuite next to the fail testsuite
- create temporary directories in the fail & success testsuites
- add a function to cleanup the last unshifted directory
- don't say we're crashed when exiting with the help message
* Specify temp path for SUT so its files will be removed after cleanup.
- cleanup
- don't use getTempFile(), it will create another subdirectory that we don't clean up afterwards...
* Fix temp path usage
- creating a 'bundles' directory wherein we would keep our temporary bundle files would collide if we'd clean it up.
- create 'bundles-tmpxxxx' instead so its individual to us and we can remove it when done without problems.
* properly create & pass in a temporary directory - as we now require this.
* Remove intermediate directory recursive - for some unknown reason there may be temp files created.
* we need to unify tempfilenames here too.
* use individual suite names
* use the standart performTests to run the backup tests - so we have the proper directory and server handling from the infrastructure.
* fix temporary directory handling in the recovery tests.
* script to build debugging debian packages
* Improve test shutdown
- handle a set of options globally per testsuite, so they don't need to clone them inside.
- properly cleanup the slave instance of the replication tests after each run.
- The per testsuite options vector will fix the behaviour that after one failed testsuite
all other suites won't be cleaned up anymore.
* don't call the overal cleanup if anything failed.
* fix cleaning up of directories.
* cleanup, fix directory creation / deletion / dummy creation.
* cleanup, fix directory creation / deletion / dummy creation.
* fix tempdir handling for the recovery tests
* Added a backup test suite. This suite is supposed to entirely drop an ArangoDB _system and restore it into a fresh one. This also includes system collections.
* Added more test cases for backup suite. Now tests several authorization/rights cenarios
* Fixed RestReplication Handlers to restore _user collections Properly.
* Updated Changelog
* Added special handling of _users in Restore for MMFiles as well.
* Added JWT secret for cluster execution of this test, also added JWT secret to shutdown call
Wilfried Goesgens
Michael Hackstein
Simon
Jan
jsteemann
Jan Christoph Uhde
Dan Larkin
Frank Celler
Max Neunhoeffer