From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: [GIT PULL OSSTEST] Merge up changes from Cambridge instance.
Date: Tue, 5 May 2015 11:40:00 +0100 [thread overview]
Message-ID: <1430822400.2660.38.camel@citrix.com> (raw)
The following changes since commit 6587e4cb8f336d2c9774b3b8d3ca88d6ebbc03e2:
Reduce guest ssh check up timeout to 10s (2015-04-02 12:50:29 +0100)
are available in the git repository at:
git://xenbits.xen.org/people/ianc/osstest.git origin-cam/production
for you to fetch changes up to e7773b6573192cf683b879db438b52092b2c57f3:
Automerge of git://xenbits.xen.org/osstest.git master into production (2015-05-04 11:20:14 +0100)
This is the contents of the various patches from the "Tweaks to allow
running non-master production instances" series and some other fixes.
This has passed through the Cambridge instances own push gate and done
one subsequent automerge from the master instance's production branch.
You can see the push gate result at
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37287/
And the automerge result in
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37299/
The latter was force pushed as the only failure was a FreeBSD migration
issue which is not specific to Cambridge.
(NB master on xenbits/osstest.git is slightly behind the production
branch in the colo, that's ok though)
----------------------------------------------------------------
Ian Campbell (7):
allow instance specific settings
cambridge: Switch configuration to use osstest.xs.citrite.net
Osstest/Debian.pm: Use Fqdn hostprop when collecting host keys
Handle osstest's own local push gate in non-master production instances
cambridge: Add a crontab
cambridge: Do not try to push harness to XenProject instance output
cambridge: Stop publishing logs to chiark
xen.org (1):
Automerge of git://xenbits.xen.org/osstest.git master into production
Osstest.pm | 2 ++
Osstest/Debian.pm | 8 ++++-
ap-common | 2 ++
ap-fetch-version | 73 ++++++++++++++++++++++++++++++++++++++++++---
ap-push | 8 ++++-
cr-ensure-disk-space | 2 ++
cr-publish-flight-logs | 6 ++--
cri-args-hostlists | 4 ++-
crontab-cambridge | 5 ++++
invoke-daemon | 5 +++-
production-config | 2 ++
production-config-cambridge | 15 ++++------
12 files changed, 113 insertions(+), 19 deletions(-)
create mode 100644 crontab-cambridge
next reply other threads:[~2015-05-05 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 10:40 Ian Campbell [this message]
2015-05-05 10:43 ` [GIT PULL OSSTEST] Merge up changes from Cambridge instance Ian Campbell
2015-05-07 14:14 ` 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=1430822400.2660.38.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.