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

[Ian Campbell <ian.campbell@citrix.com>]

On Fri, 2015-07-03 at 12:26 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v3] mg-all-branch-statuses: Show how up to date each branch is"):
> > On Thu, 2015-07-02 at 17:30 +0100, Ian Jackson wrote:
> > > This is quite fault-oblivious, isn't it.  Oh well.
> > 
> > Yes, the problem is that for branches with no baseline:
> > $ ./ap-fetch-version-old linux-next ; echo $?
> > HEAD is now at 705bb44... fix
> > fatal: Couldn't find remote ref tested/linux-next
> > 128
> > $
> > 
> > And for osstest (where the tip may not be available unless you are
> > osstest@osstest);
> > ./ap-fetch-version osstest ; echo $?
> > HEAD is now at 705bb44... fix
> > fatal: Couldn't find remote ref pretest
> > fatal: The remote end hung up unexpectedly
> > 128
> > $
> 
> Right.  There's not really anything at that layer that knows to say
> "no" rather than "aargh".
> 
> > In the latter case I print "Error!" (I could do it here instead of
> > later, I just noticed).
> > 
> > Not sure what to do about the former. In both cases this obviously
> > conflates actual failures with expected failures. I'm not sure how to
> > distinguish. Perhaps I could special case baselineless trees
> > (linux-next) in ap-fetch-version-old/ap-common and special case osstest
> > here as the only tree which might plausibly have an unavailable tip?
> 
> I think that is too big a yak.

Phew!