From: Platform Team regression test user <osstest@osstest.xs.citrite.net>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [distros-debian-snapshot test] 38096: regressions - trouble: broken/fail/pass
Date: Wed, 30 Sep 2015 22:36:15 +0100 [thread overview]
Message-ID: <osstest-38096-mainreport@xen.org> (raw)
flight 38096 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38096/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-i386-current-netinst-pygrub 3 host-install(3) broken REGR. vs. 38009
test-amd64-amd64-amd64-daily-netboot-pvgrub 9 debian-di-install fail REGR. vs. 38009
test-amd64-amd64-i386-weekly-netinst-pygrub 9 debian-di-install fail REGR. vs. 38009
test-amd64-i386-i386-weekly-netinst-pygrub 9 debian-di-install fail REGR. vs. 38009
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-weekly-netinst-pygrub 13 guest-saverestore fail blocked in 38009
test-amd64-i386-amd64-weekly-netinst-pygrub 13 guest-saverestore fail like 38009
test-amd64-i386-amd64-daily-netboot-pygrub 9 debian-di-install fail like 38009
test-amd64-i386-i386-current-netinst-pygrub 9 debian-di-install fail like 38009
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-daily-netboot-pygrub 15 guest-start/debian.repeat fail never pass
test-armhf-armhf-armhf-daily-netboot-pygrub 11 migrate-support-check fail never pass
test-armhf-armhf-armhf-daily-netboot-pygrub 12 saverestore-support-check fail never pass
baseline version:
flight 38009
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-daily-netboot-pvgrub fail
test-amd64-i386-i386-daily-netboot-pvgrub pass
test-amd64-i386-amd64-daily-netboot-pygrub fail
test-armhf-armhf-armhf-daily-netboot-pygrub fail
test-amd64-amd64-i386-daily-netboot-pygrub pass
test-amd64-amd64-amd64-current-netinst-pygrub pass
test-amd64-i386-amd64-current-netinst-pygrub pass
test-amd64-amd64-i386-current-netinst-pygrub broken
test-amd64-i386-i386-current-netinst-pygrub fail
test-amd64-amd64-amd64-weekly-netinst-pygrub fail
test-amd64-i386-amd64-weekly-netinst-pygrub fail
test-amd64-amd64-i386-weekly-netinst-pygrub fail
test-amd64-i386-i386-weekly-netinst-pygrub fail
------------------------------------------------------------
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-30 21:36 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-38096-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 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).