From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 62496: regressions - FAIL
Date: Mon, 28 Sep 2015 18:30:08 +0000 [thread overview]
Message-ID: <osstest-62496-mainreport@xen.org> (raw)
flight 62496 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62496/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 15 guest-start.2 fail REGR. vs. 62363
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-armhf-armhf-xl 13 saverestore-support-check fail never pass
version targeted for testing:
xen 3a1238d7cb73bc50f9ca1abede2b7cc59ec97bcd
baseline version:
xen fa2e4d38164453f7d000cc30d6cc47ffa1d77539
Last test of basis 62363 2015-09-25 16:52:16 Z 3 days
Testing same since 62496 2015-09-28 16:52:18 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ian Campbell <ian.campbell@citrix.com>
Juergen Gross <jgross@suse.com>
Razvan Cojocaru <rcojocaru@bitdefender.com>
Ross Lagerwall <ross.lagerwall@citrix.com>
Wei Liu <wei.liu2@citrix.com>
jobs:
build-amd64 pass
build-armhf pass
build-amd64-libvirt pass
test-armhf-armhf-xl fail
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 3a1238d7cb73bc50f9ca1abede2b7cc59ec97bcd
Author: Razvan Cojocaru <rcojocaru@bitdefender.com>
Date: Mon Sep 28 17:29:45 2015 +0200
fine grained control of REP emulation optimizations
Previously, if vm_event emulation support was enabled, then REP
optimizations were disabled when emulating REP-compatible
instructions. This patch allows fine-tuning of this behaviour by
providing a dedicated libxc helper function.
Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
commit 5d3bcd64d9eb741b4d4df45de97e318fcf836c36
Author: Juergen Gross <jgross@suse.com>
Date: Mon Sep 28 17:28:35 2015 +0200
cleanup domain builder declarations and related users
There are several unused function and structure declarations in the
hypervisor related to domain building. Remove them.
Use an enum for elf_dom_parms.pae instead of just hard coding the
values when setting the information and adjust the code to use those
instead of own macros (hypervisor and tools).
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
commit b3da0f4e9a13e29e4dccfa14cd133d1a8e6ed47d
Author: Ross Lagerwall <ross.lagerwall@citrix.com>
Date: Mon Sep 28 17:28:19 2015 +0200
MAINTAINERS: fix path to p2m-ept.c
Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
(qemu changes not included)
reply other threads:[~2015-09-28 18:30 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-62496-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).