From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-mingo-tip-master test] 16764: regressions - FAIL
Date: Thu, 28 Feb 2013 08:45:15 -0500 [thread overview]
Message-ID: <20130228134515.GA31719@phenom.dumpdata.com> (raw)
In-Reply-To: <osstest-16764-mainreport@xen.org>
On Wed, Feb 27, 2013 at 10:09:33PM +0000, xen.org wrote:
> flight 16764 linux-mingo-tip-master real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/16764/
So how do I find out what the serial console had?
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-win 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 12678
> test-amd64-i386-xl 5 xen-boot fail REGR. vs. 12678
> test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-pv 5 xen-boot fail REGR. vs. 12678
> test-amd64-i386-win 7 windows-install fail REGR. vs. 12678
> test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 12678
> test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 12678
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 12678
> test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 12678
> test-amd64-i386-xl-multivcpu 7 debian-install fail like 12678
>
> Tests which did not succeed, but are not blocking:
> test-amd64-i386-xl-credit2 15 guest-stop fail never pass
> test-amd64-amd64-qemut-win 5 xen-boot fail never pass
> test-amd64-amd64-xl-qemut-win 5 xen-boot fail never pass
> test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail never pass
> test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail never pass
> test-amd64-amd64-xl-win7-amd64 5 xen-boot fail never pass
> test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail never pass
> test-amd64-i386-xl-win-vcpus1 5 xen-boot fail never pass
> test-amd64-i386-xl-qemut-win7-amd64 7 windows-install fail never pass
> test-amd64-i386-qemut-win 7 windows-install fail never pass
> test-amd64-i386-xl-qemut-win-vcpus1 7 windows-install fail never pass
> test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
> test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
> test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
> test-amd64-i386-qemut-win-vcpus1 16 leak-check/check fail never pass
> test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
> test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
>
> version targeted for testing:
> linux 9f6584a8bd729f61c01bed1bb4e0a010bf1a643f
> baseline version:
> linux d935d0f77650fea53986811ca8a2f8c726fd9857
>
> jobs:
> build-amd64 pass
> build-armhf pass
> build-i386 pass
> build-amd64-pvops pass
> build-i386-pvops pass
> test-amd64-amd64-xl fail
> test-amd64-i386-xl fail
> test-amd64-i386-rhel6hvm-amd pass
> test-amd64-i386-qemut-rhel6hvm-amd pass
> test-amd64-i386-qemuu-rhel6hvm-amd pass
> test-amd64-amd64-xl-qemut-win7-amd64 fail
> test-amd64-i386-xl-qemut-win7-amd64 fail
> test-amd64-amd64-xl-qemuu-win7-amd64 fail
> test-amd64-amd64-xl-win7-amd64 fail
> test-amd64-i386-xl-win7-amd64 fail
> test-amd64-i386-xl-credit2 fail
> test-amd64-amd64-xl-pcipt-intel fail
> test-amd64-i386-rhel6hvm-intel fail
> test-amd64-i386-qemut-rhel6hvm-intel pass
> test-amd64-i386-qemuu-rhel6hvm-intel pass
> test-amd64-i386-xl-multivcpu fail
> test-amd64-amd64-pair fail
> test-amd64-i386-pair pass
> test-amd64-amd64-xl-sedf-pin fail
> test-amd64-amd64-pv fail
> test-amd64-i386-pv pass
> test-amd64-amd64-xl-sedf fail
> test-amd64-i386-win-vcpus1 fail
> test-amd64-i386-qemut-win-vcpus1 fail
> test-amd64-i386-xl-qemut-win-vcpus1 fail
> test-amd64-i386-xl-win-vcpus1 fail
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-winxpsp3-vcpus1 fail
> test-amd64-amd64-win fail
> test-amd64-i386-win fail
> test-amd64-amd64-qemut-win fail
> test-amd64-i386-qemut-win fail
> test-amd64-amd64-xl-qemut-win fail
> test-amd64-amd64-xl-win fail
> test-amd64-i386-xend-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemuu-winxpsp3 fail
> test-amd64-i386-xend-winxpsp3 fail
> test-amd64-amd64-xl-winxpsp3 fail
>
>
> ------------------------------------------------------------
> sg-report-flight on woking.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-02-28 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 22:09 [linux-mingo-tip-master test] 16764: regressions - FAIL xen.org
2013-02-28 13:45 ` Konrad Rzeszutek Wilk [this message]
2013-02-28 14:00 ` Jan Beulich
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=20130228134515.GA31719@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ian.jackson@eu.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.