All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: osstest-admin@xenproject.org,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xen-4.5-testing test] 66666: regressions - trouble: broken/fail/pass
Date: Mon, 4 Jan 2016 13:08:26 +0000	[thread overview]
Message-ID: <1451912906.13361.79.camel@citrix.com> (raw)
In-Reply-To: <567835A002000078000C1FF8@prv-mh.provo.novell.com>

On Mon, 2015-12-21 at 09:23 -0700, Jan Beulich wrote:
> > > > On 21.12.15 at 17:06, <osstest-admin@xenproject.org> wrote:
> > flight 66666 xen-4.5-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/66666/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-qemuu-ovmf-amd64  9 debian-hvm-install fail REGR.
> > vs. 66426
> >  test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR.
> > vs. 66426
> 
> These seem to fail pretty consistently in 4.6, 4.5, and 4.4, which
> seems odd considering that no similar failure was so far seen on
> -unstable (flight 66590 included the respective commits, and while
> it has many blocked tests the ovmf ones ar not among those). The
> guest appears to not make any attempt to reboot (albeit the libxl
> log shows that shutdown got initiated), but I can't see no other
> oddities in the logs. Thoughts anyone?

The bisections all seem to have been unsuccessful (those are posted only to
the osstest-output list[0]), e.g. [1] shows that the expected baseline was
also unreliable for both cases.

I notice that qemu-X.Y-testing also seems to be suffering failures of these
cases, but there haven't been any recent passes of qemu-upstream-4.5-
testing which might have gotten a lucky pass. Last push seems to have been
in September last year.

The bisection of the same failure on the qemu-upstream-4.4-testing branch
appears to be blocked[2,3]:
    GenFw: ERROR 3000: Invalid
      Unsupported section alignment.

Which might be fallout from the Jessie update?

Ian.

[0] http://lists.xenproject.org/archives/html/osstest-output/
[1] http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-4.5-testing/test-amd64-amd64-xl-qemuu-ovmf-amd64.debian-hvm-install.html
         http://logs.test-lab.xenproject.org/osstest/results/bisect/xen-4.5-testing/test-amd64-i386-xl-qemuu-ovmf-amd64.debian-hvm-install.html
[2] http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-upstream-4.4-testing/test-amd64-amd64-xl-qemuu-ovmf-amd64.debian-hvm-install.html
    http://logs.test-lab.xenproject.org/osstest/logs/76975/build-amd64/5.ts-xen-build.log
Ian.

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

      reply	other threads:[~2016-01-04 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 16:06 [xen-4.5-testing test] 66666: regressions - trouble: broken/fail/pass osstest service owner
2015-12-21 16:23 ` Jan Beulich
2016-01-04 13:08   ` Ian Campbell [this message]

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=1451912906.13361.79.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=osstest-admin@xenproject.org \
    --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.