From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [distros-debian-sid test] 38696: trouble: preparing/queued
Date: Mon, 25 Jan 2016 09:32:32 +0000 [thread overview]
Message-ID: <osstest-38696-mainreport@xen.org> (raw)
flight 38696 distros-debian-sid running [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38696/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-i386-sid-netboot-pvgrub <none executed> queued
test-amd64-amd64-amd64-sid-netboot-pvgrub <none executed> queued
test-amd64-amd64-i386-sid-netboot-pygrub <none executed> queued
test-amd64-i386-amd64-sid-netboot-pygrub <none executed> queued
test-armhf-armhf-armhf-sid-netboot-pygrub <none executed> queued
build-armhf 2 hosts-allocate running
build-armhf-pvops 2 hosts-allocate running
build-amd64 2 hosts-allocate running
build-i386 2 hosts-allocate running
build-i386-pvops 2 hosts-allocate running
build-amd64-pvops 2 hosts-allocate running
baseline version:
flight 38654
jobs:
build-amd64 preparing
build-armhf preparing
build-i386 preparing
build-amd64-pvops preparing
build-armhf-pvops preparing
build-i386-pvops preparing
test-amd64-amd64-amd64-sid-netboot-pvgrub queued
test-amd64-i386-i386-sid-netboot-pvgrub queued
test-amd64-i386-amd64-sid-netboot-pygrub queued
test-armhf-armhf-armhf-sid-netboot-pygrub queued
test-amd64-amd64-i386-sid-netboot-pygrub queued
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xs.citrite.net/~osstest/testlogs/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Push not applicable.
reply other threads:[~2016-01-25 9:32 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-38696-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=osstest-admin@xenproject.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.