From: Platform Team regression test user <osstest@osstest.xs.citrite.net>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [distros-debian-sid test] 37972: regressions - FAIL
Date: Sat, 19 Sep 2015 12:40:24 +0100 [thread overview]
Message-ID: <osstest-37972-mainreport@xen.org> (raw)
flight 37972 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37972/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-amd64-sid-netboot-pygrub 9 debian-di-install fail REGR. vs. 37922
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-sid-netboot-pvgrub 9 debian-di-install fail like 37922
test-amd64-i386-i386-sid-netboot-pvgrub 9 debian-di-install fail like 37922
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-sid-netboot-pygrub 11 migrate-support-check fail never pass
test-armhf-armhf-armhf-sid-netboot-pygrub 12 saverestore-support-check fail never pass
baseline version:
flight 37922
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-amd64-sid-netboot-pvgrub fail
test-amd64-i386-i386-sid-netboot-pvgrub fail
test-amd64-i386-amd64-sid-netboot-pygrub fail
test-armhf-armhf-armhf-sid-netboot-pygrub pass
test-amd64-amd64-i386-sid-netboot-pygrub pass
------------------------------------------------------------
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:[~2015-09-19 11:40 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-37972-mainreport@xen.org \
--to=osstest@osstest.xs.citrite.net \
--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.