xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 59721: regressions - trouble: broken/fail/pass
Date: Mon, 20 Jul 2015 09:48:17 +0100	[thread overview]
Message-ID: <1437382097.32450.1.camel@citrix.com> (raw)
In-Reply-To: <osstest-59721-mainreport@xen.org>

On Sun, 2015-07-19 at 10:19 +0000, osstest service owner wrote:
> flight 59721 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/59721/
> 
> 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. 58965

I think we have considered discounting i386 qemu-dm as a thing we care
about, in which case we could force push this change since this was the
only fail..


> 
> Tests which are failing intermittently (not blocking):
>  test-amd64-i386-freebsd10-i386  3 host-install(3)         broken pass in 59699
>  test-amd64-i386-qemuu-rhel6hvm-amd  3 host-install(3)     broken pass in 59699
>  test-amd64-i386-rumpuserxen-i386  3 host-install(3)       broken pass in 59699
>  test-amd64-i386-qemut-rhel6hvm-intel  3 host-install(3)   broken pass in 59699
>  test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 3 host-install(3) broken pass in 59699
>  test-amd64-i386-xl            3 host-install(3)           broken pass in 59699
>  test-amd64-i386-xl-qemut-debianhvm-amd64 3 host-install(3) broken pass in 59699
>  test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken pass in 59699
>  test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 3 host-install(3) broken pass in 59699
>  test-amd64-i386-xl-qemut-win7-amd64  3 host-install(3)    broken pass in 59699
>  test-amd64-i386-xl-qemuu-win7-amd64  3 host-install(3)    broken pass in 59699
>  test-amd64-i386-xl-qemut-winxpsp3  3 host-install(3)      broken pass in 59699
>  test-amd64-i386-xl-qemuu-winxpsp3  3 host-install(3)      broken pass in 59699
>  test-armhf-armhf-xl-multivcpu 14 guest-start.2     fail in 59699 pass in 59721
>  test-amd64-amd64-xl           9 debian-install              fail pass in 59699

Some of these host-install fails are a bit worrying, but not a blocker
to a forced push IMHO.

> version targeted for testing:
>  xen                  21d9b079e53805b68047d60d28cde224d09bbb40
> baseline version:
>  xen                  c40317f11b3f05e7c06a2213560c8471081f2662
> 
> Last test of basis    58965  2015-06-29 02:08:30 Z   20 days
> Failing since         58974  2015-06-29 15:11:59 Z   19 days   25 attempts
> Testing same since    59681  2015-07-18 00:10:50 Z    1 days    3 attempts

Ian.

  reply	other threads:[~2015-07-20  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 10:19 [xen-unstable test] 59721: regressions - trouble: broken/fail/pass osstest service owner
2015-07-20  8:48 ` Ian Campbell [this message]
2015-07-20  8:59   ` Jan Beulich
2015-07-20 12:22   ` 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=1437382097.32450.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).