[PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Campbell]

Using report_find_push_age_info allows us to provide counts of
attempts since the last baseline on current tip as well as the first
attempt of each of those.

Since everything serialises on the repo lock I didn't bother trying to
parallelise anything.

It's a little terse to keep it in 80 chars.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
v2: Use new report_find_push_age_info functionality, output condensed.

v3: - Correctly quote parameters to printf, so empty ones don't misalign the
      rest.
    - Drop dates in favour of number of days, and n/a in those cases
    - Print "Error!" if no tip is available and "UpToDate" if tip==basis.

v4: - Simplify $onevar, dropping $dflt, dropping export, subsuming
      $oneflightvar.
    - Right justify some stuff
    - s/UpToDate/same/
    - Simplify some pointless or complex shell conditionals

time with an recently updates set of Repos says:

57.34user 28.28system 5:34.16elapsed 25%CPU (0avgtext+0avgdata 47256maxresident)k
100216inputs+600outputs (673major+2332436minor)pagefaults 0swaps

So it's not quick...

Example output:
Branch                       Basis    Tip      #Tip #Tot 1stTip     1stNew
libvirt                      d10a5f58 28540794    0   11   n/a          9 days
linux-3.0                    e1c63f9f 5dba9ddd    2    9     3 days   870 days
linux-3.10                   b3d78448 same
linux-3.14                   762167f9 same
linux-3.16                   26749e75 same
linux-3.18                   d048c068 ea5dd38e    5    5     3 days     3 days
linux-3.4                    bb4a05a0 cf1b3dad   17  163    12 days   213 days
linux-4.1                    b953c0d2 6a010c0a    0    0   n/a        n/a
linux-arm-xen                64972ceb same
linux-linus                  6aaf0da8 9bdc771f    0    1   n/a          1 day
linux-mingo-tip-master       d935d0f7 21316d69    0   16   n/a       1175 days
linux-next                            e58c2435    0  219   n/a        448 days
osstest                      15d2dd50 Error!      0    -   n/a        n/a
ovmf                         3735017c 0bb5d7a5    0    1   n/a          0 days
qemu-mainline                d2966f80 35360642    0    1   n/a          0 days
qemu-upstream-4.2-testing    d2382550 same
qemu-upstream-4.3-testing    efae5e0f same
qemu-upstream-4.4-testing    32226f42 same
qemu-upstream-4.5-testing    d9552b0a same
qemu-upstream-unstable       c4a962ec same
rumpuserxen                  30d72f3f 3b91e449   62  114    78 days   150 days
seabios                      f24eb2f8 6cfebb4e    0    0   n/a        n/a
xen-4.0-testing              2692df2a same
xen-4.1-testing              40feff87 same
xen-4.2-testing              38fcda22 same
xen-4.3-testing              e7c02297 same
xen-4.4-testing              6c1cb3db same
xen-4.5-testing              e3bd3cef same
xen-unstable                 c40317f1 9379af08    0    5   n/a          3 days
---
 mg-all-branch-statuses | 120 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 120 insertions(+)
 create mode 100755 mg-all-branch-statuses

diff --git a/mg-all-branch-statuses b/mg-all-branch-statuses
new file mode 100755
index 0000000..8b86e3b
--- /dev/null
+++ b/mg-all-branch-statuses
@@ -0,0 +1,120 @@
+#!/bin/bash
+# -*- bash -*-
+#
+# Prints the status of each branch
+#
+# Usage:
+#    ./mg-all-branch-statuses [BRANCH....]
+#
+# If no BRANCHes specified, does all that are normally run by
+# cr-daily-branch or out of crontab.
+
+# This is part of "osstest", an automated testing framework for Xen.
+# Copyright (C) 2009-2014 Citrix Inc.
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+set -e
+
+. cri-common
+
+mkdir -p tmp
+
+if [ $# = 0 ]; then
+   set `./mg-list-all-branches`
+fi
+
+gather_info()
+{
+    local branch=$1; shift
+    local basis=$1;  shift
+    local tip=$1;    shift
+
+    select_xenbranch
+
+    local info=`perl -we '
+	use Osstest::Executive;
+	use Osstest;
+	use Data::Dumper;
+	open DEBUG, ">/dev/null" or die $!;
+	#open DEBUG, ">&STDERR" or die $!;
+	csreadconfig();
+	my ($branch,$tree,$basis,$tip) = @ARGV;
+	print DEBUG "branch=$branch tree=$tree basis=$basis tip=$tip\n";
+	my $info = report_find_push_age_info([qw(real adhoc play)],
+					      undef, [($branch)],
+					      $tree, $basis, $tip);
+	print DEBUG Dumper $info;
+	my $onevar = sub {
+		my ($var,$val) = @_;
+		$val //= "";
+		print uc($var)."=\"$val\";\n";
+	};
+	$onevar->($_, $info->{$_}//"-")
+		foreach qw(CountTip CountAfterBasis);
+	foreach my $flight (qw(Basis FirstAfterBasis FirstTip)) {
+		$onevar->("${flight}_${_}", $info->{$flight}{$_})
+			foreach qw(flight started);
+	}
+' "$branch" "$tree" "$basis" "$tip"`
+    eval $info
+}
+
+days_since() # Must output 10 characters
+{
+    then=$1 ; shift
+
+    if [ -z "$then" ] ; then
+	echo "  n/a     "
+	return
+    fi
+
+    local now=$(date +%s)
+    local days=$(( ($now - $then) / 86400 ))
+
+    if [ $days -eq 1 ] ; then
+	printf "%5d day " $days
+    else
+	printf "%5d days" $days
+    fi
+}
+
+printf "%-28s %-8s %-8s %-9s %-10s %-10s\n" \
+	"Branch" "Basis" "Tip" "#Tip #Tot" "1stTip" "1stNew"
+
+for branch in $@; do
+    basis=`./ap-fetch-version-old $branch 2>/dev/null || true`
+    tip=`./ap-fetch-version $branch 2>/dev/null || true`
+
+    gather_info "$branch" "$basis" "$tip"
+
+    basis=${basis:0:8}
+
+    tip=${tip:0:8}
+    : ${tip:=Error!}
+
+    printf "%-28s %-8s " "${branch}" "${basis}"
+
+    if [ x$basis != x$tip ] ; then
+	tipsince=$(days_since "$FIRSTTIP_STARTED")
+	newsince=$(days_since "$FIRSTAFTERBASIS_STARTED")
+
+	printf "%-8s  %3s  %3s %10s %10s" "${tip}" \
+	       "$COUNTTIP" "$COUNTAFTERBASIS" "$tipsince" "$newsince"
+    else
+	printf "same"
+    fi
+
+    printf "\n"
+done
-- 
2.1.4

Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Jackson]

Ian Campbell writes ("[PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"):
> Using report_find_push_age_info allows us to provide counts of
> attempts since the last baseline on current tip as well as the first
> attempt of each of those.
> 
> Since everything serialises on the repo lock I didn't bother trying to
> parallelise anything.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Do you want to provide a cron job to run this weekly, or something ?

Ian.

Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Campbell]

On Fri, 2015-07-03 at 14:40 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"):
> > Using report_find_push_age_info allows us to provide counts of
> > attempts since the last baseline on current tip as well as the first
> > attempt of each of those.
> > 
> > Since everything serialises on the repo lock I didn't bother trying to
> > parallelise anything.
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> 
> Do you want to provide a cron job to run this weekly, or something ?

Given the "NN days" I was thinking more like daily, otherwise "NN days"
is more like "+= up to 7".

Where would be a good place to run it from? Is $HOME/testing.git#master
always up to date after an osstest harness pass? (I think we can
tolerate the occasional update under foot).

Ian.

Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Jackson]

Ian Campbell writes ("Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"):
> On Fri, 2015-07-03 at 14:40 +0100, Ian Jackson wrote:
> > Do you want to provide a cron job to run this weekly, or something ?
> 
> Given the "NN days" I was thinking more like daily, otherwise "NN days"
> is more like "+= up to 7".

Sure.

> Where would be a good place to run it from? Is $HOME/testing.git#master
> always up to date after an osstest harness pass?

No, it isn't - it's only updated by the machinery in cr-for-branches.
cr-for-branches enters $HOME/testing.git and updates it each time it's
run, but...

> (I think we can tolerate the occasional update under foot).

... that's not ideal.

Perhaps we should make a new $HOME/for-maintjobs.git which can run
other kinds of not-particularly-long-running jobs.

You could use cr-for-branches from $HOME/testing.git to invoke it.
cr-for-branches will do any necessary update and take the lock.
  BRANCHES=maintjobs ./cr-for-branches . -w ./cr-all-branch-statuses ''
which would run (in $HOME/./for-maintjobs.git):
  ./cr-all-branch-statuses maintjobs

Ian.

Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Campbell]

On Fri, 2015-07-03 at 15:43 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"):
> > On Fri, 2015-07-03 at 14:40 +0100, Ian Jackson wrote:
> > > Do you want to provide a cron job to run this weekly, or something ?
> > 
> > Given the "NN days" I was thinking more like daily, otherwise "NN days"
> > is more like "+= up to 7".
> 
> Sure.
> 
> > Where would be a good place to run it from? Is $HOME/testing.git#master
> > always up to date after an osstest harness pass?
> 
> No, it isn't - it's only updated by the machinery in cr-for-branches.
> cr-for-branches enters $HOME/testing.git and updates it each time it's
> run, but...
> 
> > (I think we can tolerate the occasional update under foot).
> 
> ... that's not ideal.
> 
> Perhaps we should make a new $HOME/for-maintjobs.git which can run
> other kinds of not-particularly-long-running jobs.
> 
> You could use cr-for-branches from $HOME/testing.git to invoke it.
> cr-for-branches will do any necessary update and take the lock.
>   BRANCHES=maintjobs ./cr-for-branches . -w ./cr-all-branch-statuses ''
> which would run (in $HOME/./for-maintjobs.git):
>   ./cr-all-branch-statuses maintjobs

Should it not be:

BRANCHES=all-branch-statuses ./cr-for-branches . -w ./cr-maintjobs ''
which ends up calling
./cr-maintjobs all-branch-status
which in turn calls (from a "case $1") the new mg- from this patch?

Or maybe we rename it to mj- (for maintjob) and have cr-maintjobs call
mj-$1.

Would using ~osstest/daemons-testing.git for this be an intolerable
bodge?

Ian.

Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is

[Ian Jackson]

Ian Campbell writes ("Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"):
> Should it not be:
> 
> BRANCHES=all-branch-statuses ./cr-for-branches . -w ./cr-maintjobs ''
> which ends up calling
> ./cr-maintjobs all-branch-status
> which in turn calls (from a "case $1") the new mg- from this patch?

We probably don't need one tree for each maintenance job.  Here the
value in BRANCHES corresponds to a for-THING.git.

> Would using ~osstest/daemons-testing.git for this be an intolerable
> bodge?

Yes.  We don't want to update that without some care.

Ian.