From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: More force pushes (xen-4.5-testing, xen-unstable, qemu-mainline)
Date: Mon, 13 Apr 2015 15:14:40 +0100 [thread overview]
Message-ID: <21803.53072.60053.458135@mariner.uk.xensource.com> (raw)
In-Reply-To: <osstest-50373-mainreport@xen.org>, <osstest-50390-mainreport@xen.org>, <osstest-50391-mainreport@xen.org>
Here are some more which I propose to force push. In each case I show
all the blocking tests mentioned in the osstest test report.
osstest service user writes ("[xen-4.5-testing test] 50373: regressions - FAIL"):
> flight 50373 xen-4.5-testing real [real]
...
> test-amd64-i386-freebsd10-amd64 14 guest-localmigrate/x10 fail in 50317 REGR. vs. 50268
...
> version targeted for testing:
> xen 0b754fb3ed6b7b6d0f2e1f7c1877d3c0a7da2168
osstest service user writes ("[xen-unstable test] 50390: regressions - FAIL"):
> flight 50390 xen-unstable real [real]
> test-amd64-i386-freebsd10-i386 13 guest-localmigrate fail REGR. vs. 36514
> test-amd64-i386-freebsd10-amd64 15 guest-localmigrate.2 fail REGR. vs. 36514
...
> version targeted for testing:
> xen 123c7793797502b222300eb710cd3873dcca41ee
osstest service user writes ("[qemu-mainline test] 50391: regressions - FAIL"):
> flight 50391 qemu-mainline real [real]
...
> test-amd64-i386-freebsd10-i386 13 guest-localmigrate fail REGR. vs. 36709
> test-amd64-i386-freebsd10-amd64 15 guest-localmigrate.2 fail REGR. vs. 36709
> version targeted for testing:
> qemuu 58c24a4775ef7ccf16cfcd695753dfdf149fe29d
These are all FreeBSD migration tests. These seem to be failing much
more often in the new colo. As I say I don't know why this is. We
hope to fix it with the FreeBSD 10.1 update which Roger has submitted
and which is currently in the osstest self-push-gate.
In the general case they fail after a number of successful runs. In
each case the symptom is that the guest simply doesn't come back onto
the network after the one of the migrations. I double checked
http://logs.test-lab.xenproject.org/osstest/logs/50391/test-amd64-i386-freebsd10-amd64/info.html
and as with the earlier tests there doesn't seem to be any hints in
any of the logs.
These are all localhost migrations. This rules out a problem with the
colo infrastructure dropping or not honouring gratuitous ARP or MAC
address migration, since the guest's MAC and IP address remain (from
the infrastructure's point of view) on the same switch port.
Ian.
next prev parent reply other threads:[~2015-04-13 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 23:24 [qemu-mainline test] 50391: regressions - FAIL osstest service user
2015-04-12 19:55 ` [xen-unstable test] 50390: " osstest service user
2015-04-11 2:09 ` [xen-4.5-testing test] 50373: " osstest service user
2015-04-13 14:14 ` Ian Jackson [this message]
2015-04-14 9:58 ` More force pushes (xen-4.5-testing, xen-unstable, qemu-mainline) Jan Beulich
2015-04-14 11:11 ` Ian Jackson
2015-04-13 14:18 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=21803.53072.60053.458135@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.