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

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Mon, 2015-06-29 at 13:25 +0100, Ian Jackson wrote:
> 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.

Right. I started off simply wondering which branches were up to date or
not, not wondering why that might be so...

> 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 ?

2 sounds tricky, especially since there could potentially be several.

In general commit timestamps can be a bit misleading, since various
things preserve them even over long periods of time before they are
published and they don't necessarily correspond at all with when
something became visible in the tree one is looking at.

Maybe better than nothing though.

>  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 ?

You mean out of all 6 options you think 5 is all we need?

The date of the of the flight which established the current baseline
seems like a no-brainer (I suppose that is #4).

I'm not really sure what date of a flight relating to tip would be most
useful, first try of something newer (#5?) vs most recent attempt (#6).
Maybe even the _number_ of bites of the cherry would be useful?



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