From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [linux-linus test] 26036: trouble: broken/fail/pass
Date: Mon, 28 Apr 2014 09:14:01 +0100 [thread overview]
Message-ID: <osstest-26036-mainreport@xen.org> (raw)
flight 26036 linux-linus real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/26036/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pcipt-intel <none executed> broken
test-amd64-i386-qemuu-rhel6hvm-intel 1 xen-build-check(1) running [st=running!]
test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) running [st=running!]
test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) running [st=running!]
test-amd64-i386-qemut-rhel6hvm-amd 1 xen-build-check(1) running [st=running!]
test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl 1 xen-build-check(1) running [st=running!]
test-amd64-amd64-xl-sedf <none executed> broken
test-amd64-i386-xl-multivcpu 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl-credit2 1 xen-build-check(1) running [st=running!]
test-amd64-i386-qemut-rhel6hvm-intel 1 xen-build-check(1) running [st=running!]
test-amd64-i386-freebsd10-i386 1 xen-build-check(1) running [st=running!]
test-amd64-amd64-xl <none executed> broken
test-amd64-amd64-xl-sedf-pin <none executed> broken
test-amd64-i386-freebsd10-amd64 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl-qemuu-ovmf-amd64 1 STARTING running [st=running!]
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 1 STARTING running [st=running!]
test-amd64-amd64-xl-winxpsp3 <none executed> broken
test-amd64-i386-xl-qemuu-winxpsp3 1 xen-build-check(1) running [st=running!]
test-amd64-amd64-pair 1 STARTING running [st=running!]
test-amd64-amd64-xl-qemut-win7-amd64 1 STARTING running [st=running!]
test-amd64-i386-xl-qemut-win7-amd64 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl-win7-amd64 1 STARTING running [st=running!]
test-amd64-i386-xl-qemuu-win7-amd64 1 STARTING running [st=running!]
test-amd64-amd64-xl-qemuu-ovmf-amd64 <none executed> broken
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 1 xen-build-check(1) running [st=running!]
test-amd64-amd64-xl-win7-amd64 <none executed> broken
test-amd64-amd64-xl-qemut-winxpsp3 <none executed> broken
build-i386 2 host-install(2) broken REGR. vs. 12557
build-i386-pvops 2 host-install(2) broken REGR. vs. 12557
build-amd64 1 hosts-allocate running [st=running!]
build-amd64-pvops 1 hosts-allocate running [st=running!]
test-amd64-i386-xl-winxpsp3-vcpus1 1 STARTING running [st=running!]
test-amd64-i386-pair 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl-qemut-winxpsp3 1 xen-build-check(1) running [st=running!]
test-amd64-i386-xl-winxpsp3 1 STARTING running [st=running!]
test-amd64-amd64-xl-qemuu-win7-amd64 <none executed> broken
test-amd64-amd64-xl-qemuu-winxpsp3 <none executed> broken
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl 9 guest-start fail blocked in 12557
version targeted for testing:
linux 9a60ee117bbeaf2fb9a02ea80a6bdbc2811ca4d2
baseline version:
linux c16fa4f2ad19908a47c63d8fa436a1178438c7e7
------------------------------------------------------------
7524 people touched revisions under test,
not listing them all
------------------------------------------------------------
jobs:
build-amd64 broken
build-armhf pass
build-i386 broken
build-amd64-pvops broken
build-armhf-pvops pass
build-i386-pvops broken
test-amd64-amd64-xl broken
test-armhf-armhf-xl fail
test-amd64-i386-xl broken
test-amd64-i386-rhel6hvm-amd broken
test-amd64-i386-qemut-rhel6hvm-amd broken
test-amd64-i386-qemuu-rhel6hvm-amd broken
test-amd64-i386-freebsd10-amd64 broken
test-amd64-amd64-xl-qemuu-ovmf-amd64 broken
test-amd64-i386-xl-qemuu-ovmf-amd64 broken
test-amd64-amd64-xl-qemut-win7-amd64 broken
test-amd64-i386-xl-qemut-win7-amd64 broken
test-amd64-amd64-xl-qemuu-win7-amd64 broken
test-amd64-i386-xl-qemuu-win7-amd64 broken
test-amd64-amd64-xl-win7-amd64 broken
test-amd64-i386-xl-win7-amd64 broken
test-amd64-i386-xl-credit2 broken
test-amd64-i386-freebsd10-i386 broken
test-amd64-amd64-xl-pcipt-intel broken
test-amd64-i386-rhel6hvm-intel broken
test-amd64-i386-qemut-rhel6hvm-intel broken
test-amd64-i386-qemuu-rhel6hvm-intel broken
test-amd64-i386-xl-multivcpu broken
test-amd64-amd64-pair broken
test-amd64-i386-pair broken
test-amd64-amd64-xl-sedf-pin broken
test-amd64-amd64-xl-sedf broken
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 broken
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 broken
test-amd64-i386-xl-winxpsp3-vcpus1 broken
test-amd64-amd64-xl-qemut-winxpsp3 broken
test-amd64-i386-xl-qemut-winxpsp3 broken
test-amd64-amd64-xl-qemuu-winxpsp3 broken
test-amd64-i386-xl-qemuu-winxpsp3 broken
test-amd64-amd64-xl-winxpsp3 broken
test-amd64-i386-xl-winxpsp3 broken
------------------------------------------------------------
sg-report-flight on osstest.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.
(No revision log; it would be 2645224 lines long.)
reply other threads:[~2014-04-28 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-26036-mainreport@xen.org \
--to=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.