From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: [PATCH OSSTEST 2/2] cambridge: arrange to test each new baseline Date: Mon, 13 Jul 2015 09:16:32 +0100 Message-ID: <1436775392-14815-2-git-send-email-ian.campbell@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: ian.jackson@eu.citrix.com Cc: Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Provide a new cr-daily-branch setting OSSTEST_BASELINES_ONLY which causes it to only attempt to test the current baseline (if it is untested) and never the tip version. Such tests will not result in any push. Add a cronjob to Cambridge which runs in this manner, ensuring that there will usually be some sort of reasonably up to date baseline for any given branch which can be used for comparisons in adhoc testing or bisections. This will also give us some data on the success of various branches on the set of machines in Cambridge, which can be useful/interesting. Signed-off-by: Ian Campbell --- cr-daily-branch | 13 ++++++++++++- crontab-cambridge | 1 + 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/cr-daily-branch b/cr-daily-branch index 7e3e69e..dac28ea 100755 --- a/cr-daily-branch +++ b/cr-daily-branch @@ -85,7 +85,11 @@ check_tested () { "$@" } -if [ "x$OSSTEST_NO_BASELINE" != xy ] ; then +if [ "x$OSSTEST_BASELINES_ONLY" = xy ] ; then + force_baseline=baselines-only + wantpush=false + skipidentical=true +elif [ "x$OSSTEST_NO_BASELINE" != xy ] ; then testedflight=`check_tested --revision-$tree="$OLD_REVISION"` if [ "x$testedflight" = x ]; then @@ -258,6 +262,13 @@ any, is the most recent actually tested revision. END ;; + baselines-only) + #subject-prefix="[... ] " + cat >> $heading </dev/null -- 2.1.4