From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 5/5] cambridge: Stop publishing logs to chiark
Date: Thu, 2 Apr 2015 12:25:13 +0100 [thread overview]
Message-ID: <1427973913.4037.57.camel@citrix.com> (raw)
In-Reply-To: <21789.9472.250952.263646@mariner.uk.xensource.com>
On Thu, 2015-04-02 at 12:16 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 5/5] cambridge: Stop publishing logs to chiark"):
> > http://osstest.cam.xci-test.com/~osstest/testlogs already exists and
> > points to the live logs directory, so switch PubBaseUrl to that in the
> > Cambridge config such that email reports etc contain it. This won't be
> > externally accessible but I think that won't matter now that the
> > master production instance is elsewhere.
> >
> > Arrange that cr-publish-flight-logs doesn't publish the corresponding
> > thing if either LogsPublish or ResultsPublish is not set, and unset
> > them in the Cambridge config.
> >
> > Likewise arrange that cr-ensure-disk-space doesn't do anything if the
> > configuration variable passed as an option is not set, and unset
> > Publish (the base for {Logs,Results}Publish) in the Cambridge config.
> >
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > ---
> > cr-ensure-disk-space | 2 ++
> > cr-publish-flight-logs | 4 ++--
> > production-config-cambridge | 6 +-----
> > 3 files changed, 5 insertions(+), 7 deletions(-)
> >
> > diff --git a/cr-ensure-disk-space b/cr-ensure-disk-space
> > index 0ee84c7..84b1890 100755
> > --- a/cr-ensure-disk-space
> > +++ b/cr-ensure-disk-space
> > @@ -40,6 +40,8 @@ die unless @ARGV==1;
> >
> > our ($cfgbase) = @ARGV;
> >
> > +exit 0 unless $cfgbase;
> >
> > csreadconfig();
>
> Don't you mean "unless $c{$cfgbase}" ?
I think I do, yes.
> And then it has to come after csreadconfig. (Did you test this ?)
I was running in standalone mode, so I don't think this code will have
actually been run, I was relying on my ability to reason about the code,
which apparently failed :-/.
Shall I run an adhoc flight with this change in it?
Ian.
next prev parent reply other threads:[~2015-04-02 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 15:09 [PATCH OSSTEST 0/5] Tweaks to allow running non-master production instances Ian Campbell
2015-04-01 15:10 ` [PATCH OSSTEST 1/5] cri-args-hostslists: allow instance specific settings Ian Campbell
2015-04-02 10:52 ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 2/5] Handle osstest's own local push gate in non-master production instances Ian Campbell
2015-04-02 11:13 ` Ian Jackson
2015-04-02 11:21 ` Ian Campbell
2015-04-01 15:10 ` [PATCH OSSTEST 3/5] cambridge: Add a crontab Ian Campbell
2015-04-02 11:13 ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 4/5] cambridge: Do not try to push harness to XenProject instance output Ian Campbell
2015-04-02 11:13 ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 5/5] cambridge: Stop publishing logs to chiark Ian Campbell
2015-04-02 11:16 ` Ian Jackson
2015-04-02 11:25 ` Ian Campbell [this message]
2015-04-02 15:34 ` 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=1427973913.4037.57.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.