Once a week should be sufficient for these tests. Perhaps in the
future we will want to increase the frequency for the suites under
active development (testing, unstable)

For now run this on the Citrix Cambridge instance until the XenProject
instance has sufficient capacity.

Signed-off-by: Ian Campbell <ian.campb...@citrix.com>
---
v8: Switch to hard tabs split to previous patch.
v7: Replaces "distros: Run a flight over the weekend."
    Now run in Cambridge
    Run separate flight per-suite
    Dropped Ack
---
 crontab-cambridge | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/crontab-cambridge b/crontab-cambridge
index e0c3eff..7d3ed57 100644
--- a/crontab-cambridge
+++ b/crontab-cambridge
@@ -2,4 +2,9 @@ 
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
 MAILTO=ian.jack...@citrix.com,ian.campb...@eu.citrix.com
 # m            h       dom mon dow     command
 4-59/30                *       * * *           cd testing.git && 
BRANCHES='osstest'                    ./cr-for-branches branches -q 
"./cr-daily-branch --real"
+46             7       * * 6           cd testing.git && 
BRANCHES='distros-debian-snapshot'    ./cr-for-branches branches -w 
"./cr-daily-branch --real"
+46             7       * * 5           cd testing.git && 
BRANCHES='distros-debian-sid'         ./cr-for-branches branches -w 
"./cr-daily-branch --real"
+46             7       * * 4           cd testing.git && 
BRANCHES='distros-debian-jessie'      ./cr-for-branches branches -w 
"./cr-daily-branch --real"
+46             7       * * 3           cd testing.git && 
BRANCHES='distros-debian-wheezy'      ./cr-for-branches branches -w 
"./cr-daily-branch --real"
+46             7       * * 2           cd testing.git && 
BRANCHES='distros-debian-squeeze'     ./cr-for-branches branches -w 
"./cr-daily-branch --real"
 3              4       * * *           savelog -c28 
testing.git/tmp/cr-for-branches.log >/dev/null
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to