This is an automated email from the ASF dual-hosted git repository.

ctubbsii pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 75b6ef3 for  (#113)
75b6ef3 is described below

commit 75b6ef383ae980d24a1c4e2280928ef3cb860f9f
Author: Russell Carter <>
AuthorDate: Thu Sep 26 16:05:31 2019 -0400 for  (#113)
---                 |  3 +++
 test/automation/ | 17 +++++++++++++++++
 2 files changed, 20 insertions(+)

diff --git a/ b/
index 88b0009..e5e4f78 100644
--- a/
+++ b/
@@ -238,6 +238,9 @@ test and produce json result files.
 There are some utilities for working with the json result files, run the 
`performance` script
 with no options to see them.
+## Automated Cluster Testing
+See the [](/test/automation/
 [modules]: core/src/main/resources/randomwalk/modules
 [image]: core/src/main/resources/randomwalk/modules/Image.xml
diff --git a/test/automation/ b/test/automation/
new file mode 100644
index 0000000..06a74ea
--- /dev/null
+++ b/test/automation/
@@ -0,0 +1,17 @@
+# Automated Cluster Testing
+Testing a snapshot version of Accumulo on a cluster using this respository 
requires many repetive steps.  Luckily, there is script that automates this 
using [Muchos].  This script is found in 
+Before running the script, edit []( All 
repositories are set to the master branch of the corresponding Apache project 
by default. You can change these values to your specific forks and branches as 
+A path to `muchos.props` is required in order to run the script. You can find 
the required configurations and an example of `muchos.props` [in the official 
Fluo-Muchos readme][Muchos].
+### Execution takes no arguments as followed: 
+    ./
+### Things to consider:
+* The script will read from the `MUCHOS_PROPS` environment variable if 
+* Accumulo versions between `muchos.props` and `pom.xml` file of a given 
Accumulo branch should be consistent.
+* Accumulo and Fluo-Muchos will be installed locally in a temporary directory 
under `/tmp`, which is typically cleared by the operating system periodically 
(system-specific, possibly on reboots, daily, weekly, etc.).

Reply via email to