From: osstest service user <osstest@xenbits.xen.org>
To: xen-devel@lists.xensource.com, rumpkernel-builds@freelists.org
Cc: ian.jackson@eu.citrix.com
Subject: [rumpuserxen test] 50657: trouble: blocked/broken/pass
Date: Mon, 20 Apr 2015 12:51:02 +0000 [thread overview]
Message-ID: <osstest-50657-mainreport@xen.org> (raw)
flight 50657 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/50657/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REGR. vs. 33866
build-amd64-pvops 3 host-install(3) broken REGR. vs. 33866
build-i386 3 host-install(3) broken REGR. vs. 33866
Regressions which are regarded as allowable (not blocking):
build-i386-xsm 3 host-install(3) broken blocked in 33866
build-amd64-xsm 3 host-install(3) broken blocked in 33866
Tests which did not succeed, but are not blocking:
test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a
test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a
build-amd64-rumpuserxen 1 build-check(1) blocked n/a
build-i386-rumpuserxen 1 build-check(1) blocked n/a
version targeted for testing:
rumpuserxen 3b91e44996ea6ae1276bce1cc44f38701c53ee6f
baseline version:
rumpuserxen 30d72f3fc5e35cd53afd82c8179cc0e0b11146ad
------------------------------------------------------------
People who touched revisions under test:
Antti Kantee <pooka@iki.fi>
Ian Jackson <Ian.Jackson@eu.citrix.com>
Martin Lucina <martin@lucina.net>
Wei Liu <liuw@liuw.name>
------------------------------------------------------------
jobs:
build-amd64-xsm broken
build-i386-xsm broken
build-amd64 broken
build-i386 broken
build-amd64-pvops broken
build-i386-pvops pass
build-amd64-rumpuserxen blocked
build-i386-rumpuserxen blocked
test-amd64-amd64-rumpuserxen-amd64 blocked
test-amd64-i386-rumpuserxen-i386 blocked
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/osstest/pub/logs
images: /home/osstest/pub/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-step build-i386-xsm host-install(3)
broken-step build-amd64-xsm host-install(3)
broken-step build-amd64 host-install(3)
broken-step build-amd64-pvops host-install(3)
broken-step build-i386 host-install(3)
Not pushing.
(No revision log; it would be 535 lines long.)
reply other threads:[~2015-04-20 12:51 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-50657-mainreport@xen.org \
--to=osstest@xenbits.xen.org \
--cc=ian.jackson@eu.citrix.com \
--cc=rumpkernel-builds@freelists.org \
--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.