[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [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:

> > +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`
> 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

And for osstest (where the tip may not be available unless you are
./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

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?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.