From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
ian.jackson@eu.citrix.com,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 57852: regressions - FAIL
Date: Fri, 5 Jun 2015 11:48:20 +0100 [thread overview]
Message-ID: <1433501300.7108.208.camel@citrix.com> (raw)
In-Reply-To: <5571858C020000780008132E@mail.emea.novell.com>
On Fri, 2015-06-05 at 10:18 +0100, Jan Beulich wrote:
> >>> On 05.06.15 at 11:07, <ian.campbell@citrix.com> wrote:
> > From:
> > http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64
> > -xl-qemuu-win7-amd64.xen-4.4-testing.html
> > http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64
> > -xl-qemuu-win7-amd64.xen-4.5-testing.html
> > it looks like none of the stable branches suffer from the install issue.
> > I'd be inclined to discount any possible link with the migration issue
> > based on that.
>
> Generally I would agree, but it strikes me as extremely odd that
> (a) stable trees face only the migration issue, while unstable only
> faces the install one,
http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64-xl-qemuu-win7-amd64.xen-unstable.html shows some migration failures too (in a batch though, not spread out).
Wouldn't the migration issue be potentially blocked by the install one?
> (b) a tree as old as 4.3 (receiving only security updates) developed
> this migration issue (I went into more detail on this in a reply to flight
> 57474's report).
>
> > WRT the move to the colo, flights in 5xxxx are in the new one, while
> > 3xxxx are in the old one,
> > http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64
> > -xl-qemuu-win7-amd64.xen-unstable.html
> > shows that things seemed ok for 8 consecutive runs after the move
> > (ignoring blockages).
>
> And when it went live, all systems being in use now got immediately
> deployed?
All the flights in the new colo seem to have been on fiano[01].
But having looked at the page again the early success was all on fiano0
while the later failures were all on fiano1.
fiano[01] are supposedly identical hardware.
This might be simply explained by osstest's stickiness for jobs on hosts
where they are failing. I'll run a few adhoc jobs on fiano0 using 57852
as a template so we can see if that's the case.
Ian.
next prev parent reply other threads:[~2015-06-05 10:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 12:01 [xen-unstable test] 57852: regressions - FAIL osstest service user
2015-06-05 8:45 ` Ian Campbell
2015-06-05 9:00 ` Jan Beulich
2015-06-05 9:07 ` Ian Campbell
2015-06-05 9:18 ` Jan Beulich
2015-06-05 10:48 ` Ian Campbell [this message]
2015-06-05 16:46 ` Ian Campbell
2015-06-08 8:07 ` Jan Beulich
2015-06-08 8:53 ` Ian Campbell
2015-06-08 9:15 ` Jan Beulich
2015-06-08 9:27 ` Ian Campbell
2015-06-08 10:17 ` Jan Beulich
2015-06-08 14:43 ` Ian Jackson
2015-06-08 12:16 ` Ian Campbell
2015-06-08 12:19 ` Andrew Cooper
2015-06-08 12:24 ` Jan Beulich
2015-06-09 8:26 ` Ian Campbell
2015-06-09 9:29 ` Jan Beulich
2015-06-10 8:50 ` Ian Campbell
2015-06-10 9:36 ` Jan Beulich
2015-06-10 11:01 ` Ian Campbell
2015-06-10 11:48 ` Jan Beulich
2015-06-10 12:56 ` Ian Campbell
2015-06-10 13:23 ` Jan Beulich
2015-06-10 13:45 ` Jan Beulich
2015-06-10 14:08 ` Ian Campbell
2015-06-11 7:02 ` Jan Beulich
2015-06-11 8:45 ` Ian Campbell
2015-06-15 8:57 ` Ian Campbell
2015-06-15 9:03 ` Jan Beulich
2015-06-10 14:34 ` Ian Campbell
2015-06-10 15:59 ` Jan Beulich
2015-06-10 16:18 ` Don Slutz
2015-06-10 18:00 ` Ian Campbell
2015-06-08 13:50 ` Konrad Rzeszutek Wilk
2015-06-08 14:02 ` Ian Campbell
2015-06-08 14:47 ` Ian Jackson
2015-06-08 15:21 ` Konrad Rzeszutek Wilk
2015-06-08 15:29 ` Ian Campbell
2015-06-08 10:10 ` 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=1433501300.7108.208.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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.