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

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("[PATCH OSSTEST v2] 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.
> 
> It's a little terse to keep it in 80 chars.

Thanks.  This is useful.

> I did wonder about adding this to some cronjob or something.
> 
> Example output:
> Branch                       Basis    Tip      #Tip #Tot 1stTip     1stNew
> libvirt                   d10a5f58 ebd62eba    0    9 ????-??-?? 2015-06-23
> linux-3.0                 e1c63f9f 5dba9ddd    1    8 2015-06-30 2013-02-13

These ????-??-?? are quite visually noisy.  And the ISO dates are not
ideal for reading - how about printing a number of days ago instead ?

> linux-next                2e0a48c9             0  219 ????-??-?? 2014-04-10

I'm not sure what this means.  219 in #Tot would normally be a problem
and `1stNew' is from 2014.  But linux-next is not fast-forwarding.
And there's allegedly no tip although I think maybe you mean there is
no basis.

> osstest                   15d2dd50             0    - ????-??-?? ????-??-??

Is the lack of a Tip here a bug ?

> xen-4.5-testing           e3bd3cef e3bd3cef

You could replace one copy of `e3bd3cef' with `same' or soemthing.

Ian.

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