flight 108103 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108103/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 5 xen-buildfail REGR. vs. 107636
build-arm64
flight 108093 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108093/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-xl
On Wed, Apr 26, 2017 at 05:39:57PM +0100, George Dunlap wrote:
>On 26/04/17 01:52, Chao Gao wrote:
>> I compared the maximum of #entry in one list and #event (adding entry to
>> PI blocking list) with and without the three latter patches. Here
>> is the result:
>> --
flight 108081 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108081/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 108022
test-amd64-i386-xl-q
flight 108095 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108095/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 17 guest-start/win.repeat fail REGR.
vs. 107606
Tests whi
On 04/26/2017 02:34 PM, osstest service owner wrote:
flight 107696 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/107696/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 5 libvirt-build
branch xen-unstable
xenbranch xen-unstable
job build-i386
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: qemuu git://git.q
flight 108076 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108076/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 107636
build-arm64-xsm
flight 108068 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108068/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 17 guest-start/win.repeat fail REGR.
vs. 107900
Tests w
On Mon, 1 May 2017, Bhupinder Thakur wrote:
> Hi Stefano,
>
> >> diff --git a/tools/libxl/libxl_console.c b/tools/libxl/libxl_console.c
> >> index 446e766..ef3bd44 100644
> >> --- a/tools/libxl/libxl_console.c
> >> +++ b/tools/libxl/libxl_console.c
> >> @@ -67,6 +67,9 @@ int libxl_console_exec(lib
flight 108058 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108058/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358
Tests which are faili
flight 108052 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108052/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 17 guest-start/win.repeat fail REGR.
vs. 107606
Tests whi
Hi Razvan,
Sure thing. Thanks anyway :)
Cheers,
~Sergej
On 05/01/2017 04:38 PM, Razvan Cojocaru wrote:
> On 04/30/2017 10:48 PM, Sergej Proskurin wrote:
>> The function p2m_mem_access_check_and_get_page in mem_access.c
>> translates a gva to an ipa by means of the hardware functionality
>> imp
flight 108051 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108051/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-xl
On 04/30/2017 10:48 PM, Sergej Proskurin wrote:
> The function p2m_mem_access_check_and_get_page in mem_access.c
> translates a gva to an ipa by means of the hardware functionality
> implemented in the function gva_to_ipa. If mem_access is active,
> hardware-based gva to ipa translation might fail,
flight 108069 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108069/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-buildfail REGR. vs. 107640
build-amd64-libvirt
Hi Stefano,
>> diff --git a/tools/libxl/libxl_console.c b/tools/libxl/libxl_console.c
>> index 446e766..ef3bd44 100644
>> --- a/tools/libxl/libxl_console.c
>> +++ b/tools/libxl/libxl_console.c
>> @@ -67,6 +67,9 @@ int libxl_console_exec(libxl_ctx *ctx, uint32_t domid, int
>> cons_num,
>> cas
flight 71244 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71244/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-sid-netboot-pvgrub 10 guest-start fail blocked in 71223
test-amd64-i386-i38
On Thu, Apr 27, 2017 at 09:13:16PM -0500, Eric Blake wrote:
> Libvirt would like to be able to distinguish between a SHUTDOWN
> event triggered solely by guest request and one triggered by a
> SIGTERM or other action on the host. While qemu_kill_report() is
> already able to tell whether a shutdow
flight 108059 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/108059/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 107636
build-arm64-xsm
20 matches
Mail list logo
