From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v8 2/2] mg-all-branch-statuses: Show how up to date each branch is
Date: Mon, 13 Jul 2015 12:41:13 +0100 [thread overview]
Message-ID: <1436787673.7019.117.camel@citrix.com> (raw)
In-Reply-To: <1436452236-3334-2-git-send-email-ian.campbell@citrix.com>
On Thu, 2015-07-09 at 15:30 +0100, Ian Campbell wrote:
> 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.
>
> cron infrastructure is added to run this in a new
> $HOME/for-maintjobs.git on a daily basis and push the output to the
> location given in the Publish config variable, if it is set (it is set
> in production but not for cambridge).
This is now live at:
http://logs.test-lab.xenproject.org/osstest/results/all-branch-statuses.txt
It includes:
maintjobs Error! 0 - n/a n/a
I'm considering giving mg-all-branch-statuses a new optional argument
which if present will be a path to a directory which will be used to
filter the branches by checking that a for-$branch.git directory exists
there. cr-all-branch-statuses would pass $HOME/branches.
What do you think?
Ian.
next prev parent reply other threads:[~2015-07-13 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 14:30 [PATCH OSSTEST v8 1/2] cr-publish-flight-logs: allow publishing only the Results Ian Campbell
2015-07-09 14:30 ` [PATCH OSSTEST v8 2/2] mg-all-branch-statuses: Show how up to date each branch is Ian Campbell
2015-07-09 15:35 ` Ian Jackson
2015-07-13 11:41 ` Ian Campbell [this message]
2015-07-09 15:34 ` [PATCH OSSTEST v8 1/2] cr-publish-flight-logs: allow publishing only the Results Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436787673.7019.117.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.