All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
	xen-devel@lists.xensource.com
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [xen-unstable test] 76919: regressions - FAIL
Date: Wed, 6 Jan 2016 11:19:18 +0000	[thread overview]
Message-ID: <1452079158.7292.34.camel@citrix.com> (raw)
In-Reply-To: <1452078861.7292.31.camel@citrix.com>

On Wed, 2016-01-06 at 11:14 +0000, Ian Campbell wrote:
> On Tue, 2016-01-05 at 02:26 +0000, osstest service owner wrote:
> > flight 76919 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/76919/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-
> > install fail REGR. vs. 66879
> 
> ISTR someone (Wei?) at some point saying that a 32-bit stubdom (as used
> here) isn't actually something we wish to support. Shall we either drop
> this test altogether or mark it as allow? Or will someone investigate why
> it apparently can't find its disks.
> 
> http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/xen-unstable.html

4.6 exhibits the same pattern, as do linux-3.14 and 3.16:
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/xen-4.6-testing.html
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/linux-3.14.html
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/linux-3.16.html

(more or less, 3.14 seems to have never gotten lucky)

But recent linux 3.18 and 4.1 results look relatively positive:
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/linux-3.18.html
http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/linux-4.1.html

Could this have been a dom0 kernel issue, previously masked by merlot*
specific issues, which is since fixed (or less prevalent at least)?

Ian.

> seems to suggest it has a very low probability of success (both merlot
> and
> italia failed dozens of times before passing)
> 
> Nothing in the xen.git range bf925a9f1254..8e4d18e113c9 looks especially
> relevant.
> 
> Bisection couldn't reproduce the basis pass:
> http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-unstable/t
> est-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm.debian-hvm-
> install.html
> 
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-06 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  2:26 [xen-unstable test] 76919: regressions - FAIL osstest service owner
2016-01-06 11:14 ` Ian Campbell
2016-01-06 11:19   ` Ian Campbell [this message]
2016-01-06 14:37   ` Wei Liu

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=1452079158.7292.34.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=wei.liu2@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.