From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [examine test] 126473: FAIL
Date: Sat, 25 Aug 2018 01:27:17 +0000 [thread overview]
Message-ID: <osstest-126473-mainreport@xen.org> (raw)
flight 126473 examine real [real]
http://logs.test-lab.xenproject.org/osstest/logs/126473/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
examine-baroque1 2 hosts-allocate broken REGR. vs. 125522
examine-joubertin1 2 hosts-allocate broken REGR. vs. 125522
examine-rimava1 2 hosts-allocate broken REGR. vs. 125522
examine-fiano0 2 hosts-allocate broken REGR. vs. 125522
examine-godello1 2 hosts-allocate broken REGR. vs. 125522
examine-italia0 2 hosts-allocate broken REGR. vs. 125522
examine-fiano1 2 hosts-allocate broken REGR. vs. 125522
examine-huxelrebe1 2 hosts-allocate broken REGR. vs. 125522
examine-debina1 2 hosts-allocate broken REGR. vs. 125522
examine-godello0 2 hosts-allocate broken REGR. vs. 125522
examine-elbling0 2 hosts-allocate broken REGR. vs. 125522
examine-elbling1 2 hosts-allocate broken REGR. vs. 125522
examine-albana1 2 hosts-allocate broken REGR. vs. 125522
examine-chardonnay0 2 hosts-allocate broken REGR. vs. 125522
examine-pinot0 2 hosts-allocate broken REGR. vs. 125522
examine-pinot1 2 hosts-allocate broken REGR. vs. 125522
examine-baroque0 2 hosts-allocate broken REGR. vs. 125522
examine-joubertin0 2 hosts-allocate broken REGR. vs. 125522
examine-chardonnay1 2 hosts-allocate broken REGR. vs. 125522
Tests which did not succeed, but are not blocking:
examine-albana0 4 memdisk-try-append fail like 125522
baseline version:
flight 125522
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
examine-albana0 pass
examine-albana1 fail
examine-baroque0 fail
examine-baroque1 fail
examine-arndale-bluewater pass
examine-cubietruck-braque pass
examine-chardonnay0 fail
examine-chardonnay1 fail
examine-debina0 pass
examine-debina1 fail
examine-elbling0 fail
examine-elbling1 fail
examine-fiano0 fail
examine-fiano1 fail
examine-cubietruck-gleizes pass
examine-godello0 fail
examine-godello1 fail
examine-huxelrebe1 fail
examine-italia0 fail
examine-joubertin0 fail
examine-joubertin1 fail
examine-arndale-lakeside pass
examine-arndale-metrocentre pass
examine-cubietruck-metzinger pass
examine-cubietruck-picasso pass
examine-pinot0 fail
examine-pinot1 fail
examine-rimava1 fail
examine-arndale-westfield pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Push not applicable.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-08-25 1:27 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-126473-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/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).