* [xen-unstable-smoke test] 96182: regressions - FAIL
@ 2016-06-23 17:58 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2016-06-23 17:58 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 96182 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96182/
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. 96177
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
version targeted for testing:
xen 9808c130f04ff331aca23beee262f3d83eb46e55
baseline version:
xen 6a35f1e1fb03bbb957828f9f2cf8bfc47df95ee6
Last test of basis 96177 2016-06-23 13:02:08 Z 0 days
Testing same since 96182 2016-06-23 16:07:29 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Dirk Behme <dirk.behme@de.bosch.com>
Jan Beulich <jbeulich@suse.com>
Julien Grall <julien.grall@arm.com>
Kevin Tian <kevin.tian@intel.com>
Stefano Stabellini <sstabellini@kernel.org>
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 9808c130f04ff331aca23beee262f3d83eb46e55
Author: Dirk Behme <dirk.behme@de.bosch.com>
Date: Wed Jun 22 13:49:07 2016 +0200
xen/arm: drivers: scif: Don't overwrite firmware settings
Besides the 14MHz external clock, the SCIF might be clocked by an
internal 66MHz clock. If this is the case, the current clock source
selection breaks this configuration. Same for the settings done by
the firmware for data bits, stop bits and parity.
Completely drop this and rely on the settings done by the firmware.
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
Reviewed-by: Julien Grall <julien.grall@arm.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
commit 892a43cd9996a45875de14c06828dea859039430
Author: Dirk Behme <dirk.behme@de.bosch.com>
Date: Wed Jun 22 13:49:06 2016 +0200
xen/arm: drivers: scif: Remove dead code
The two struct members baud and clock_hz are in the end read only
variables nowhere used for anything useful. Removing them makes
the code much simpler without changing any functionality.
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
Reviewed-by: Julien Grall <julien.grall@arm.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
commit 3d5cb5a81f8c68e74be4074db1777741f3059409
Author: Julien Grall <julien.grall@arm.com>
Date: Thu Jun 23 17:50:19 2016 +0200
arm: rename gmfn_to_mfn to gfn_to_mfn and use gfn/mfn typesafe
The correct acronym for a guest physical frame is gfn. Also use
the recently introduced typesafe gfn/mfn to avoid mixing the two
different kind of frame.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
commit b45a4f1ed6c865fc1222d71fc82e4b61771b261b
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Jun 23 17:48:45 2016 +0200
x86emul: support MOVBE and CRC32
The former in an attempt to at least gradually support all simple data
movement instructions. The latter just because it shares the opcode
with the former.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
commit d86ad7cb287b5ea05cfee20cdd277005d771886f
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Jun 23 17:47:44 2016 +0200
VMX: ensure MSR index enum and array remain in sync
... by using dedicated initializers. Also add an ASSERT() to make sure
unintentional addition of holes to the array gets noticed. Ditch
MSR_INDEX_SIZE as redundant with VMX_MSR_COUNT.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Kevin Tian <kevin.tian@intel.com>
commit 3528b5b4c3b1695ecc7af5622b32042aafbdf6f4
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Jun 23 17:46:55 2016 +0200
VMX: use non-atomic bitops to manage MSR state
All host_msr_state accesses are solely on the owning CPU, and all
guest_msr_state ones solely when the vCPU is current or being switched
to. This, btw, is also in line with the use of find_first_set_bit()
(which would be bogus if ->flags could get updated behind its back).
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Kevin Tian <kevin.tian@intel.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-06-23 17:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-23 17:58 [xen-unstable-smoke test] 96182: regressions - FAIL osstest service owner
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).