From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 113133: trouble: broken/pass
Date: Thu, 07 Sep 2017 19:48:56 +0000 [thread overview]
Message-ID: <osstest-113133-mainreport@xen.org> (raw)
flight 113133 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113133/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 <job status> broken
test-arm64-arm64-xl-xsm <job status> broken
build-arm64-pvops <job status> broken
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64-pvops 2 hosts-allocate broken like 113039
build-arm64-pvops 3 capture-logs broken like 113039
build-arm64 2 hosts-allocate broken like 113039
build-arm64 3 capture-logs broken like 113039
test-armhf-armhf-xl 13 migrate-support-check fail never pass
test-armhf-armhf-xl 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
version targeted for testing:
xen e9cb0d1d0eb3a9e4d8b97432c9246cdfbb3b0309
baseline version:
xen 6dfb43d6f2cd8ea6274d203ca00ecfc7c565f11a
Last test of basis 113039 2017-09-04 15:02:08 Z 3 days
Failing since 113052 2017-09-05 13:01:29 Z 2 days 25 attempts
Testing same since 113131 2017-09-07 16:01:58 Z 0 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Alexandru Isaila <aisaila@bitdefender.com>
Andrew Cooper <andrew.cooper3@citrix.com>
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Ian Jackson <Ian.Jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Olaf Hering <olaf@aepfle.de>
Tamas K Lengyel <tamas@tklengyel.com>
Wei Liu <wei.liu2@citrix.com>
Yi Sun <yi.y.sun@linux.intel.com>
jobs:
build-amd64 pass
build-arm64 broken
build-armhf pass
build-amd64-libvirt pass
build-arm64-pvops broken
test-armhf-armhf-xl pass
test-arm64-arm64-xl-xsm broken
test-amd64-amd64-xl-qemuu-debianhvm-i386 pass
test-amd64-amd64-libvirt 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
broken-job build-arm64 broken
broken-job test-arm64-arm64-xl-xsm broken
broken-job build-arm64-pvops broken
broken-step build-arm64-pvops hosts-allocate
broken-step build-arm64-pvops capture-logs
broken-step build-arm64 hosts-allocate
broken-step build-arm64 capture-logs
Not pushing.
(No revision log; it would be 368 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-09-07 19:48 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-113133-mainreport@xen.org \
--to=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).