Re: [Xen-devel] [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances
On Wed, 2015-04-15 at 14:47 +0100, Ian Jackson wrote:
Ian Campbell writes (Re: [PATCH OSSTEST v2 0/5] Tweaks to allow running
non-master production instances):
Since you have now acked everything may I push to the Cambridge branch
(once the VM is working again)?
Yes.
(modulo if you want me to make the minor change discussed on 1/5 now or
not)
Either way is fine.
I created the file on both sites, but I didn't change this patch since
we are pushing this to Cambridge first if it does cause an issue when
merged back into mainline it'll be annoying to cleanup, better to let a
future change go through the usual mainline gate alone.
I've just pushed the following, which is a bunch of stuff from upstream
osstest and these five patches, to Cambridge pretest and then:
$ rm branches/for-osstest.git/stop
Lets see if the VM stays up long enough to test them!
Ian.
$ git log --oneline a623769..41ac504
41ac504 cambridge: Stop publishing logs to chiark
bcc9c68 cambridge: Do not try to push harness to XenProject instance output
6196543 cambridge: Add a crontab
7007b0a Handle osstest's own local push gate in non-master production instances
5926203 cri-args-hostslists: allow instance specific settings
eff0c77 cambridge: Set HostProp_DhcpWatchMethod back to woking
8f1dc3f ts-host-ping-check: Do not run if host is being reused
ba691ef standalone: Add --dry-run option for run-job.
effe70a tcl: Handle environment variables which are unset.
4a938b2 Merge branch 'production' of osstest.test-lab:/home/osstest/testing
into wip
2d1aa25 production-config: Adjust LogsMinSpaceMby to not be half of the VM's
disk
5ae027f Merge branch 'colo.2015-03-31' of xenbits.xen.org:/home/iwj/ext/osstest
into queue
4bf33f8 production-config*: Set HostnameSortSwapWords as appropriate
e2008dc (Re)Add production config for Cambridge instance
f89d6ac Osstest.pm: Add use IO::File
0ab790c ts-host-install: honour arch-specific boot append properties
e654ecc ts-host-ping-check: New ubiquitous test step
a80d215 sg-report-flight: Produce better output for running jobs.
6ec412e sg-report-flight: Sort email output by results, not job name
6cbaf65 cs-adjust-flight: Support negation of foo-specs
fdddba7 config: turn off HostnameSortSwapWords by default
ea335bc start/stop the guest 10 times in the standard test jobs
4d6bbe0 README.dev: Document steps after restarting ms-ownerdaemon
97fa466 uboot: make flask loading address host property
ab441f3 uboot: do not use readlink on xsm policy
dce7456 Merge remote-tracking branch 'origin/incoming' into wip.colo
bf3a468 Remove passthrough tests
7d87cf0 Empty commit to force test run
bc50a13 Configs: Replace xenbits.xensource.com with xenbits.xen.org
da7c22d mg-branch-setup: Make initial push optional in mg-branch-setup
831c94e ts-debian-install: Honour DebianMirrorProxy, HttpProxy
a141aca production-config: Configuration for new production colo
310c5b5 Branches: Rename incoming branch to production
b294e14 config defaults: Do not use woking for dhcp leases
2fedf11 ts-kernel-build: enable CONFIG_SCSI_HPSA
347eadf ts-kernel-build: enable CONFIG_SCSI_ISCI
591ed47 ts-kernel-build: Document a hacky way to get CONFIG_... options
4d0dba4 HostnameSortSwapWords: Make name order mangling configurable
a4debc0 mg-execute-flight: New -P (publish) option
41e9bf0 cr-ensure-disk-space: Honour different config for published log expiry
2ad7b3f cr-ensure-disk-space: Operate locally entirely separately.
2563b91 cr-ensure-disk-space: Permit argument to specify local directory.
dd6be0f cr-ensure-disk-space: Fix -n option
43a0974 cr-ensure-disk-space: Take argument for what to clean
1d25a8c cr-ensure-disk-space: Do listing of flights on target.
d6edb5d cr-ensure-disk-space: Do df check on target.
438637a cr-ensure-disk-space: Break out ontarget
fdc2659 cr-ensure-disk-space: Move LogsPublish decomposition up
d8b13ac cr-ensure-disk-space: Emacs perl-mode syntax workaround
f16e621 daemons: Allow QueueDaemon and OwnerDaemon to run on different hosts
0ff3bb1 target_cmd_build: Honour $c{HttpProxy}
a11fc63 HostDB Executive: Option to suppress configdb
2b5aa29 readglobalconfig: Support Include
f5b354a readglobalconfig: Break out $readcfg as a sub
bf2b666 Debian mirrors: Support proxy, and default to ftp.debian.org if
specified
eb805e8 pxe setup: mg-hosts mkpxedir has -n (dry run) option
a865cc2 pxe setup: New TftpPxeTemplatesReal feature
14e0e8d Osstest: Default config: Use foreach for empty defaults
bbcce4d mg-hosts: Provide new power subcommand
68f35a1 pxe setup: Define %name% in templates
e8a5b82 PDU: pdu-msw: Support APC v6 firmware
9705c37 PDU: pdu-msw: Split $read_oid and $write_oid
0fb0a00 PDU: msw: support arbitrary arguments
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Re: [Xen-devel] [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances
On Wed, 2015-04-15 at 12:33 +0100, Ian Jackson wrote: Ian Campbell writes ([PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances): WRT applying this I think normally we should apply such changes to the upstream production instance and let them filter through, but in this case I think it would be better to push my ad-hoc tested branch (based on upstream cambridge: Set HostProp_DhcpWatchMethod back to woking, reference by pull req below) to the local Cambridge pretest, allow it to automerge upstream master into that and test the result. Once that passes I will send a pull-request to merge the result back into the mainline. I think you are probably right, since this particular series contains the merging-from-an-upsream machinery. Since you have now acked everything may I push to the Cambridge branch (once the VM is working again)? (modulo if you want me to make the minor change discussed on 1/5 now or not) Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances
Ian Campbell writes (Re: [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances): Since you have now acked everything may I push to the Cambridge branch (once the VM is working again)? Yes. (modulo if you want me to make the minor change discussed on 1/5 now or not) Either way is fine. Thanks, Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
[Xen-devel] [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances
Now that the Cambridge osstest instance is no longer the XenProject master instance it needs some tweaks to allow us to keep using it for local testing. Since v2 I have now tested this in as close to how the osstest user in Cambridge would, but in my own $HOME/testing.git and it appears to do the right things. As part of that I made various fixes, in particular to the ap-fetch-version stuff. A test report email from my adhoc flight is below. (the Cambridge VM is current knackered so the link doesn't work and it is only internally available now). WRT applying this I think normally we should apply such changes to the upstream production instance and let them filter through, but in this case I think it would be better to push my ad-hoc tested branch (based on upstream cambridge: Set HostProp_DhcpWatchMethod back to woking, reference by pull req below) to the local Cambridge pretest, allow it to automerge upstream master into that and test the result. Once that passes I will send a pull-request to merge the result back into the mainline. Ian. The following changes since commit eff0c7780505a610a39f995fb132318bd3f8647b: cambridge: Set HostProp_DhcpWatchMethod back to woking (2015-04-02 12:03:58 +0100) are available in the git repository at: git://xenbits.xen.org/people/ianc/osstest.git non-prod-instances-v2 for you to fetch changes up to 76c499329a6a47117c2c397433b1f950f35dd741: cambridge: Stop publishing logs to chiark (2015-04-04 08:53:06 +0100) Ian Campbell (5): cri-args-hostslists: allow instance specific settings 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 Osstest.pm | 2 ++ ap-common | 2 ++ ap-fetch-version| 25 ++--- ap-push | 8 +++- cr-ensure-disk-space| 2 ++ cr-publish-flight-logs | 6 -- cri-args-hostlists | 4 +++- crontab-cambridge | 5 + production-config | 2 ++ production-config-cambridge | 9 + 10 files changed, 50 insertions(+), 15 deletions(-) create mode 100644 crontab-cambridge ---BeginMessage--- flight 37075 osstest play [play] http://osstest.cam.xci-test.com/~osstest/testlogs/logs/37075/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 9 debian-installfail REGR. vs. 36584 test-armhf-armhf-xl-xsm 6 xen-boot fail like 36584 test-amd64-i386-pair21 guest-migrate/src_host/dst_host fail like 36584 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl-multivcpu 18 capture-logs(18)broken never pass test-armhf-armhf-xl 18 capture-logs(18) broken never pass test-armhf-armhf-xl-sedf 18 capture-logs(18) broken never pass test-armhf-armhf-libvirt-xsm 7 capture-logs(7) broken never pass test-armhf-armhf-xl-sedf-pin 18 capture-logs(18) broken never pass test-armhf-armhf-xl-credit2 18 capture-logs(18) broken never pass test-armhf-armhf-xl-midway 18 capture-logs(18) broken never pass test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail never pass test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass test-amd64-amd64-libvirt-xsm 11 guest-start fail never pass test-amd64-amd64-xl-xsm 11 guest-start fail never pass test-amd64-i386-xl-xsm 11 guest-start fail never pass test-amd64-i386-libvirt-xsm 11 guest-start fail never pass test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-i386-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12 migrate-support-checkfail never pass test-armhf-armhf-xl-sedf 12 migrate-support-checkfail never pass test-armhf-armhf-libvirt-xsm 6 xen-boot fail never pass test-armhf-armhf-xl-sedf-pin 12 migrate-support-checkfail never pass test-armhf-armhf-xl-credit2 12 migrate-support-checkfail never pass test-armhf-armhf-libvirt 15 guest-start/debian.repeatfail never pass
Re: [Xen-devel] [PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances
Ian Campbell writes ([PATCH OSSTEST v2 0/5] Tweaks to allow running non-master production instances): WRT applying this I think normally we should apply such changes to the upstream production instance and let them filter through, but in this case I think it would be better to push my ad-hoc tested branch (based on upstream cambridge: Set HostProp_DhcpWatchMethod back to woking, reference by pull req below) to the local Cambridge pretest, allow it to automerge upstream master into that and test the result. Once that passes I will send a pull-request to merge the result back into the mainline. I think you are probably right, since this particular series contains the merging-from-an-upsream machinery. Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
