flight 83042 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83042/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 3 host-install(3) broken REG
On Fri, Feb 19, 2016 at 08:40:49AM -0800, Andy Lutomirski wrote:
> On Fri, Feb 19, 2016 at 6:15 AM, Luis R. Rodriguez wrote:
> > Any failure on the x86 init path can be catastrophic.
> > A simple shift of a call from one place to another can
> > easily break things. Likewise adding a new call to
>
flight 83043 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83043/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 82482
Regress
CONFIG_ARM_32 and CONFIG_ARM_64 is defined by Kconfig.
Signed-off-by: Doug Goldstein
---
CC: Ian Campbell
CC: Stefano Stabellini
---
xen/include/asm-arm/config.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/xen/include/asm-arm/config.h b/xen/include/asm-arm/config.h
index a1b968d..
CONFIG_X86 is defined by Kconfig when building for x86.
Signed-off-by: Doug Goldstein
---
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
---
xen/include/asm-x86/config.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/xen/include/asm-x86/config.h b/xen/include/asm-x86/config.h
index a45
On 02/20/2016 04:27 AM, Gonglei wrote:
It's possible for a race condition to exist between xennet_open() and
talk_to_netback(). After invoking netfront_probe() then other
threads or processes invoke xennet_open (such as NetworkManager)
immediately may trigger BUG_ON(). Besides, we also should re
flight 83119 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83119/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 guest-saverestorefail never pass
test-armhf-armhf-libvirt 12 migrate-sup
On 19/02/16 22:03, Joao Martins wrote:
> On 02/19/2016 05:55 PM, Andrew Cooper wrote:
>> On 19/02/16 17:29, Joao Martins wrote:
>>> On 02/05/2016 01:41 PM, Andrew Cooper wrote:
For the featureset to be a useful object, it needs a stable
interpretation, a
property which is missing fr
On 20/02/16 15:34, Doug Goldstein wrote:
> CONFIG_X86 is defined by Kconfig when building for x86.
>
> Signed-off-by: Doug Goldstein
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
flight 83116 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83116/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 60684
build-amd6
On 02/20/2016 04:17 PM, Andrew Cooper wrote:
> On 19/02/16 22:03, Joao Martins wrote:
>> On 02/19/2016 05:55 PM, Andrew Cooper wrote:
>>> On 19/02/16 17:29, Joao Martins wrote:
On 02/05/2016 01:41 PM, Andrew Cooper wrote:
> For the featureset to be a useful object, it needs a stable
>>>
Le lun. 1 févr. 2016 à 07:35, Jan Beulich a écrit :
> >>> On 01.02.16 at 13:28, wrote:
> > On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
> >> >>> On 30.01.16 at 02:47, wrote:
> >> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> >> >> (re-adding xen-devel)
> >> >>
On 20/02/16 17:39, Joao Martins wrote:
>
> and given that this
> is exposed on both sysctl and libxl (through libxl_hwcap) shouldn't its
> size
> match the real one (boot_cpu_data.x86_capability) i.e. NCAPINTS ?
> Additionally I
> see that libxl_hwcap is also hardcoded to
flight 83118 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83118/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
build-amd64-rumpuserx
flight 83120 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83120/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 81632
flight 83135 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83135/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemut-debianhvm-amd64 15 guest-localmigrate/x10 fail in
83003 pass in 83135
test-armhf-ar
Le mar. 26 janv. 2016 à 05:52, Jan Beulich a écrit :
> >>> On 25.01.16 at 22:49, wrote:
> > The case is 1) disabling iommu for IGD, unilaterally since i915 + gm45
> > doesn't play well together. Iommu is still desired to isolate usb and
> > network devices, so we don't want to disable iommu comp
flight 83159 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83159/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 3 host-install(3) broken REGR. vs. 82911
test-amd64-i386-libvir
18 matches
Mail list logo