From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 106361: regressions - trouble: broken/fail/pass
Date: Thu, 02 Mar 2017 10:46:03 +0000 [thread overview]
Message-ID: <osstest-106361-mainreport@xen.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3854 bytes --]
flight 106361 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106361/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 106320
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
build-arm64 5 xen-build fail never pass
build-arm64-pvops 5 kernel-build fail never pass
version targeted for testing:
xen f14ce1a13455bfc3fb7b33c185e3e49749d68e28
baseline version:
xen 1a0ab02e342cfd80decd72606c94479e4b309a3c
Last test of basis 106320 2017-03-01 20:01:41 Z 0 days
Testing same since 106361 2017-03-02 09:01:12 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Olaf Hering <olaf@aepfle.de>
Wei Liu <wei.liu2@citrix.com>
jobs:
build-amd64 pass
build-arm64 fail
build-armhf pass
build-amd64-libvirt pass
build-arm64-pvops fail
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
Not pushing.
------------------------------------------------------------
commit f14ce1a13455bfc3fb7b33c185e3e49749d68e28
Author: Wei Liu <wei.liu2@citrix.com>
Date: Wed Mar 1 12:32:26 2017 +0000
MAINTAINERS: add Marek as maintainer of python bindings
Marek has kindly agreed to step up and co-maintain the python bindings.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
commit d31828e348e7b7229d7ecb32f7f0bee7f125e61e
Author: Olaf Hering <olaf@aepfle.de>
Date: Wed Mar 1 12:27:08 2017 +0000
tools/libxendevicemodel: define O_CLOEXEC
Some libc headers don't have O_CLOEXEC, we need to take care of it by
defining to 0 (on the ground that such glibc might barf on O_CLOEXEC).
Fixes e7745d8ef5 ("tools/libxendevicemodel: introduce a Linux-specific
implementation")
Signed-off-by: Olaf Hering <olaf@aepfle.de>
Acked-by: Wei Liu <wei.liu2@citrix.com>
commit 34b05462d93f06f9a08caf98b7aed865f6b796bd
Author: Wei Liu <wei.liu2@citrix.com>
Date: Wed Mar 1 11:07:24 2017 +0000
acpi: check if mapping is valid before reading / writing
If acpi_map_os_memory has failed, return early with AE_ERROR.
Coverity-ID: 1401601
Coverity-ID: 1401602
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-03-02 10:46 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-106361-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).