From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v2 2/5] Handle osstest's own local push gate in non-master production instances
Date: Mon, 20 Apr 2015 14:15:37 +0100 [thread overview]
Message-ID: <1429535737.25195.436.camel@citrix.com> (raw)
In-Reply-To: <1429535664.25195.435.camel@citrix.com>
On Mon, 2015-04-20 at 14:14 +0100, Ian Campbell wrote:
> I'm about to kick off an adhoc test on the Cambridge VM
Except the filer seems to have just died for the second time today. I
suspect I'll be putting a hold on this work until we can switch over to
reliable infrastructure (which is in progress AIUI)
Ian.
next prev parent reply other threads:[~2015-04-20 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 10:04 [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances Ian Campbell
2015-04-15 10:04 ` [PATCH OSSTEST v2 1/5] cri-args-hostslists: allow instance specific settings Ian Campbell
2015-04-15 11:32 ` Ian Jackson
2015-04-15 11:57 ` Ian Campbell
2015-04-15 13:47 ` Ian Jackson
2015-04-15 10:04 ` [PATCH OSSTEST v2 2/5] Handle osstest's own local push gate in non-master production instances Ian Campbell
2015-04-15 11:29 ` Ian Jackson
2015-04-20 13:14 ` Ian Campbell
2015-04-20 13:15 ` Ian Campbell [this message]
2015-04-15 10:04 ` [PATCH OSSTEST v2 3/5] cambridge: Add a crontab Ian Campbell
2015-04-15 10:04 ` [PATCH OSSTEST v2 4/5] cambridge: Do not try to push harness to XenProject instance output Ian Campbell
2015-04-15 10:04 ` [PATCH OSSTEST v2 5/5] cambridge: Stop publishing logs to chiark Ian Campbell
2015-04-15 11:31 ` Ian Jackson
2015-04-15 11:33 ` [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances Ian Jackson
2015-04-15 11:58 ` Ian Campbell
2015-04-15 13:47 ` Ian Jackson
2015-04-17 9:32 ` Ian Campbell
2015-04-17 9:40 ` [PATCH OSSTEST] cri-args-hostlists: No longer export $OSSTEST_CONFIG Ian Campbell
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=1429535737.25195.436.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.