From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 112957: regressions - trouble: broken/fail/pass
Date: Wed, 30 Aug 2017 13:49:42 +0000 [thread overview]
Message-ID: <osstest-112957-mainreport@xen.org> (raw)
flight 112957 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112957/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 12 guest-start fail REGR. vs. 112956
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 112956
build-arm64-pvops 3 capture-logs broken like 112956
build-arm64 2 hosts-allocate broken like 112956
build-arm64 3 capture-logs broken like 112956
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
version targeted for testing:
xen 2b936ea7b716dc1a13c98550f81752ab053e95c0
baseline version:
xen dab6a84aadab11f31332030a1e9f0b9282d76156
Last test of basis 112956 2017-08-30 09:56:56 Z 0 days
Testing same since 112957 2017-08-30 12:02:17 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Dario Faggioli <dario.faggioli@citrix.com>
George Dunlap <george.dunlap@citrix.com>
Jan Beulich <jbeulich@suse.com>
Tim Deegan <tim@xen.org>
jobs:
build-amd64 pass
build-arm64 broken
build-armhf pass
build-amd64-libvirt pass
build-arm64-pvops broken
test-armhf-armhf-xl fail
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-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 334 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-08-30 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 13:49 osstest service owner [this message]
2017-08-30 13:54 ` [xen-unstable-smoke test] 112957: regressions - trouble: broken/fail/pass Andrew Cooper
2017-08-30 14:15 ` George Dunlap
2017-08-31 15:53 ` Wei Liu
2017-09-02 15:39 ` Julien Grall
2017-09-04 8:46 ` George Dunlap
2017-09-05 15:50 ` Dario Faggioli
2017-09-05 22:06 ` Stefano Stabellini
2017-09-06 10:27 ` Dario Faggioli
2017-09-06 19:29 ` Stefano Stabellini
2017-09-06 23:36 ` Dario Faggioli
2017-09-07 16:05 ` Wei Liu
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-112957-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).