From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com, rumpkernel-builds@lists.sourceforge.net
Cc: ian.jackson@eu.citrix.com
Subject: [rumpuserxen test] 29548: trouble: broken/pass
Date: Fri, 1 Aug 2014 09:02:24 +0100 [thread overview]
Message-ID: <osstest-29548-mainreport@xen.org> (raw)
flight 29548 rumpuserxen real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/29548/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 3 host-install(3) broken REGR. vs. 29521
version targeted for testing:
rumpuserxen 81e3a66bde0dc534f6a965858cf1daf0965367a5
baseline version:
rumpuserxen c2eeb369ef2eb72b4d5ac0c9b2b986b2945c8fc1
------------------------------------------------------------
People who touched revisions under test:
Antti Kantee <pooka@iki.fi>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
build-amd64-rumpuserxen pass
build-i386-rumpuserxen pass
test-amd64-amd64-rumpuserxen-amd64 pass
test-amd64-i386-rumpuserxen-i386 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.
------------------------------------------------------------
commit 81e3a66bde0dc534f6a965858cf1daf0965367a5
Author: Antti Kantee <pooka@iki.fi>
Date: Wed Jul 30 12:12:54 2014 +0000
update travis urls
commit a18c746dbd656333c096fefc3cd5a7dad1c3b96e
Author: Antti Kantee <pooka@iki.fi>
Date: Wed Jul 30 12:11:39 2014 +0000
update wiki url (repo rename rumpuser-xen -> rumprun-xen)
reply other threads:[~2014-08-01 8:02 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-29548-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--cc=rumpkernel-builds@lists.sourceforge.net \
--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).