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

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("[PATCH OSSTEST v1] mg-all-branch-statuses: Show how up to 
date each branch is"):
> The osstest branch doesn't expose pretest (at least not to the machine I 
> tested
> this on), so it ends up ignored here.
> 
> Some branches (e.g. linux-next) do not record a baseline, so the script allows
> for that.
> 
> Since everything serialises on the repo lock I didn't bother trying to
> parallelise anything.
...
> Example output:
> libvirt                          d10a5f58c75e7eb5943b44cc36a1e768adb2cdb0 => 
> f7d8aa44b06e5cfa06abea4a72ee26b13754667d

This is lacking date information which is IMO critical.

It's probably fairly straightforward to search through the database or
history to find some relevant date.  What do want to know ?

 1. `Commit' timestamp of last pass ?
 2. `Commit' timestamp of first commit after last pass ?
 3. `Commit' timestamp of tip ?

 4. Start date of last flight for current baseline ?
 5. Start date of first flight after last flight for current baseline ?
 6. Start date of first flight for current tip ?

5 ?

Ian.

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