Once a week should be sufficient for this test. It involves quite a
large number of jobs so schedule it to start early on Saturday so it
can run over the weekend when, in theory, things should be quieter.
Signed-off-by: Ian Campbell <ian.campb...@citrix.com>
Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
crontab | 1 +
1 file changed, 1 insertion(+)
diff --git a/crontab b/crontab
index 5dc8675..1917ec4 100644
--- a/crontab
+++ b/crontab
@@ -6,5 +6,6 @@ MAILTO=ian.jack...@citrix.com,ian.campb...@eu.citrix.com
18 9 * * 1,3,5 cd testing.git && BRANCHES=linux-next
./cr-for-branches branches -w "./cr-daily-branch --real"
18 4 * * * cd testing.git && BRANCHES='linux-linus
linux-mingo-tip-master linux-3.0 libvirt rumpuserxen' ./cr-for-branches
branches -w "./cr-daily-branch --real"
6-59/15 * * * * cd testing.git &&
EXTRA_BRANCHES='linux-linus linux-3.0 rumpuserxen libvirt' ./cr-for-branches
bisects -w "./cr-try-bisect --real"
+46 7 * * 6 cd testing.git && BRANCHES=distros
./cr-for-branches branches -w "./cr-daily-branch --real"
#8-59/5 * * * * cd bisects/adhoc.git &&
with-lock-ex -q data-tree-lock bash -c "./cr-try-bisect-adhoc; exit $?"
3 4 * * * savelog -c28
testing.git/tmp/cr-for-branches.log >/dev/null
--
2.1.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
