* [qemu-upstream-unstable test] 116118: FAIL
@ 2017-11-13 6:44 osstest service owner
2017-11-13 11:50 ` Anthony PERARD
2017-11-13 11:52 ` Julien Grall
0 siblings, 2 replies; 5+ messages in thread
From: osstest service owner @ 2017-11-13 6:44 UTC (permalink / raw)
To: xen-devel, osstest-admin
[-- Attachment #1: Type: text/plain, Size: 13199 bytes --]
flight 116118 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/116118/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops <job status> broken in 115713
build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qcow2 19 guest-start/debian.repeat fail in 115713 pass in 116118
test-armhf-armhf-libvirt 6 xen-install fail in 116105 pass in 116118
test-amd64-amd64-libvirt-vhd 17 guest-start/debian.repeat fail in 116105 pass in 116118
test-amd64-i386-libvirt-qcow2 17 guest-start/debian.repeat fail pass in 115713
test-armhf-armhf-xl-rtds 6 xen-install fail pass in 116105
test-amd64-i386-xl-xsm 20 guest-start/debian.repeat fail pass in 116105
test-armhf-armhf-xl-vhd 15 guest-start/debian.repeat fail pass in 116105
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail REGR. vs. 114457
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail REGR. vs. 114457
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl-multivcpu 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-libvirt 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-libvirt-raw 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-vhd 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-credit2 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-cubietruck 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-rtds 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-arndale 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-libvirt-xsm 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-xsm 1 build-check(1) blocked in 115713 n/a
test-armhf-armhf-xl-rtds 13 migrate-support-check fail in 116105 never pass
test-armhf-armhf-xl-rtds 14 saverestore-support-check fail in 116105 never pass
test-armhf-armhf-libvirt 14 saverestore-support-check fail like 114457
test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 114457
test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 114457
test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
test-amd64-i386-libvirt 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-i386-libvirt-qcow2 12 migrate-support-check fail never pass
test-amd64-amd64-xl-pvhv2-amd 12 guest-start fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass
test-armhf-armhf-libvirt 13 migrate-support-check fail never pass
test-armhf-armhf-xl 13 migrate-support-check fail never pass
test-armhf-armhf-xl 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass
test-armhf-armhf-libvirt-xsm 13 migrate-support-check fail never pass
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass
test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass
test-armhf-armhf-xl-xsm 13 migrate-support-check fail never pass
test-armhf-armhf-xl-xsm 14 saverestore-support-check fail never pass
test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass
version targeted for testing:
qemuu b79708a8ed1b3d18bee67baeaf33b3fa529493e2
baseline version:
qemuu 5cd7ce5dde3f228b3b669ed9ca432f588947bd40
Last test of basis 114457 2017-10-13 09:14:56 Z 30 days
Testing same since 115703 2017-11-09 16:18:53 Z 3 days 6 attempts
------------------------------------------------------------
People who touched revisions under test:
Anthony PERARD <anthony.perard@citrix.com>
Michael Tokarev <mjt@tls.msk.ru>
Roger Pau Monne <roger.pau@citrix.com>
Roger Pau Monné <roger.pau@citrix.com>
Stefano Stabellini <sstabellini@kernel.org>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-armhf-armhf-libvirt-xsm pass
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-xl-xsm pass
test-armhf-armhf-xl-xsm pass
test-amd64-i386-xl-xsm fail
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-amd64-xl-pvhv2-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-qemuu-ws16-amd64 fail
test-amd64-i386-xl-qemuu-ws16-amd64 fail
test-armhf-armhf-xl-arndale pass
test-amd64-amd64-xl-credit2 pass
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-amd64-xl-qemuu-win10-i386 fail
test-amd64-i386-xl-qemuu-win10-i386 fail
test-amd64-amd64-qemuu-nested-intel pass
test-amd64-amd64-xl-pvhv2-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt pass
test-armhf-armhf-libvirt pass
test-amd64-i386-libvirt pass
test-amd64-amd64-xl-multivcpu pass
test-armhf-armhf-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-pygrub pass
test-amd64-i386-libvirt-qcow2 fail
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw pass
test-amd64-i386-xl-raw pass
test-amd64-amd64-xl-rtds pass
test-armhf-armhf-xl-rtds fail
test-amd64-amd64-libvirt-vhd pass
test-armhf-armhf-xl-vhd fail
------------------------------------------------------------
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
broken-job build-armhf-pvops broken
Not pushing.
------------------------------------------------------------
commit b79708a8ed1b3d18bee67baeaf33b3fa529493e2
Author: Anthony PERARD <anthony.perard@citrix.com>
Date: Tue Oct 10 11:24:18 2017 +0100
ui/gtk: Fix deprecation of vte_terminal_copy_clipboard
vte_terminal_copy_clipboard() is deprecated in VTE 0.50.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
(cherry picked from commit 70857ad6212276dcda364e36b30258222bdb31bc)
commit d957c46ff18d0d71809fd04fdc78700feacdc902
Author: Roger Pau Monne <roger.pau@citrix.com>
Date: Thu Aug 24 16:07:03 2017 +0100
xen/pt: allow QEMU to request MSI unmasking at bind time
When a MSI interrupt is bound to a guest using
xc_domain_update_msi_irq (XEN_DOMCTL_bind_pt_irq) the interrupt is
left masked by default.
This causes problems with guests that first configure interrupts and
clean the per-entry MSIX table mask bit and afterwards enable MSIX
globally. In such scenario the Xen internal msixtbl handlers would not
detect the unmasking of MSIX entries because vectors are not yet
registered since MSIX is not enabled, and vectors would be left
masked.
Introduce a new flag in the gflags field to signal Xen whether a MSI
interrupt should be unmasked after being bound.
This also requires to track the mask register for MSI interrupts, so
QEMU can also notify to Xen whether the MSI interrupt should be bound
masked or unmasked
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
Reported-by: Andreas Kinzler <hfp@posteo.de>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
(cherry picked from commit a8036336609d2e184fc3543a4c439c0ba7d7f3a2)
Release-acked-by: Julien Grall <julien.grall@linaro.org>
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-upstream-unstable test] 116118: FAIL
2017-11-13 6:44 [qemu-upstream-unstable test] 116118: FAIL osstest service owner
@ 2017-11-13 11:50 ` Anthony PERARD
2017-11-13 11:52 ` Julien Grall
1 sibling, 0 replies; 5+ messages in thread
From: Anthony PERARD @ 2017-11-13 11:50 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel
On Mon, Nov 13, 2017 at 06:44:49AM +0000, osstest service owner wrote:
> flight 116118 qemu-upstream-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/116118/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-armhf-pvops <job status> broken in 115713
> build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
This test pass in this flight. Why the fact that it was broken in an
older flight is blocking here?
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-upstream-unstable test] 116118: FAIL
2017-11-13 6:44 [qemu-upstream-unstable test] 116118: FAIL osstest service owner
2017-11-13 11:50 ` Anthony PERARD
@ 2017-11-13 11:52 ` Julien Grall
2017-11-13 11:53 ` Wei Liu
1 sibling, 1 reply; 5+ messages in thread
From: Julien Grall @ 2017-11-13 11:52 UTC (permalink / raw)
To: osstest service owner, xen-devel, Stefano Stabellini,
Anthony Perard, Wei Liu, Ian Jackson
Hi,
On 11/13/2017 06:44 AM, osstest service owner wrote:
> flight 116118 qemu-upstream-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/116118/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-armhf-pvops <job status> broken in 115713
> build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
Looking at the test result, build-armhf-pvops seems to have passed
nicely the past few weeks but one time.
So I am not sure why we are blocking here. Mostly the <job status> one.
Cheers,
[1]
http://logs.test-lab.xenproject.org/osstest/results/history/build-armhf-pvops/qemu-upstream-unstable
>
> Tests which are failing intermittently (not blocking):
> test-amd64-amd64-xl-qcow2 19 guest-start/debian.repeat fail in 115713 pass in 116118
> test-armhf-armhf-libvirt 6 xen-install fail in 116105 pass in 116118
> test-amd64-amd64-libvirt-vhd 17 guest-start/debian.repeat fail in 116105 pass in 116118
> test-amd64-i386-libvirt-qcow2 17 guest-start/debian.repeat fail pass in 115713
> test-armhf-armhf-xl-rtds 6 xen-install fail pass in 116105
> test-amd64-i386-xl-xsm 20 guest-start/debian.repeat fail pass in 116105
> test-armhf-armhf-xl-vhd 15 guest-start/debian.repeat fail pass in 116105
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail REGR. vs. 114457
> test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail REGR. vs. 114457
>
> Tests which did not succeed, but are not blocking:
> test-armhf-armhf-xl-multivcpu 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-libvirt 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-libvirt-raw 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-vhd 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-credit2 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-cubietruck 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-rtds 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-arndale 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-libvirt-xsm 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-xsm 1 build-check(1) blocked in 115713 n/a
> test-armhf-armhf-xl-rtds 13 migrate-support-check fail in 116105 never pass
> test-armhf-armhf-xl-rtds 14 saverestore-support-check fail in 116105 never pass
> test-armhf-armhf-libvirt 14 saverestore-support-check fail like 114457
> test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail like 114457
> test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 114457
> test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
> test-amd64-i386-libvirt 13 migrate-support-check fail never pass
> test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass
> test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
> test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass
> test-amd64-i386-libvirt-qcow2 12 migrate-support-check fail never pass
> test-amd64-amd64-xl-pvhv2-amd 12 guest-start fail never pass
> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
> test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass
> test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass
> test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass
> test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass
> test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass
> test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass
> test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass
> test-armhf-armhf-libvirt 13 migrate-support-check fail never pass
> test-armhf-armhf-xl 13 migrate-support-check fail never pass
> test-armhf-armhf-xl 14 saverestore-support-check fail never pass
> test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass
> test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass
> test-armhf-armhf-libvirt-xsm 13 migrate-support-check fail never pass
> test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
> test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass
> test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass
> test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
> test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass
> test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass
> test-armhf-armhf-xl-xsm 13 migrate-support-check fail never pass
> test-armhf-armhf-xl-xsm 14 saverestore-support-check fail never pass
> test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
> test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass
>
> version targeted for testing:
> qemuu b79708a8ed1b3d18bee67baeaf33b3fa529493e2
> baseline version:
> qemuu 5cd7ce5dde3f228b3b669ed9ca432f588947bd40
>
> Last test of basis 114457 2017-10-13 09:14:56 Z 30 days
> Testing same since 115703 2017-11-09 16:18:53 Z 3 days 6 attempts
>
> ------------------------------------------------------------
> People who touched revisions under test:
> Anthony PERARD <anthony.perard@citrix.com>
> Michael Tokarev <mjt@tls.msk.ru>
> Roger Pau Monne <roger.pau@citrix.com>
> Roger Pau Monné <roger.pau@citrix.com>
> Stefano Stabellini <sstabellini@kernel.org>
>
> jobs:
> build-amd64-xsm pass
> build-armhf-xsm pass
> build-i386-xsm pass
> build-amd64 pass
> build-armhf pass
> build-i386 pass
> build-amd64-libvirt pass
> build-armhf-libvirt pass
> build-i386-libvirt pass
> build-amd64-pvops pass
> build-armhf-pvops pass
> build-i386-pvops pass
> test-amd64-amd64-xl pass
> test-armhf-armhf-xl pass
> test-amd64-i386-xl pass
> test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
> test-amd64-amd64-libvirt-xsm pass
> test-armhf-armhf-libvirt-xsm pass
> test-amd64-i386-libvirt-xsm pass
> test-amd64-amd64-xl-xsm pass
> test-armhf-armhf-xl-xsm pass
> test-amd64-i386-xl-xsm fail
> test-amd64-amd64-qemuu-nested-amd fail
> test-amd64-amd64-xl-pvhv2-amd fail
> test-amd64-i386-qemuu-rhel6hvm-amd pass
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
> test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
> test-amd64-i386-freebsd10-amd64 pass
> test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
> test-amd64-i386-xl-qemuu-ovmf-amd64 pass
> test-amd64-amd64-xl-qemuu-win7-amd64 fail
> test-amd64-i386-xl-qemuu-win7-amd64 fail
> test-amd64-amd64-xl-qemuu-ws16-amd64 fail
> test-amd64-i386-xl-qemuu-ws16-amd64 fail
> test-armhf-armhf-xl-arndale pass
> test-amd64-amd64-xl-credit2 pass
> test-armhf-armhf-xl-credit2 pass
> test-armhf-armhf-xl-cubietruck pass
> test-amd64-i386-freebsd10-i386 pass
> test-amd64-amd64-xl-qemuu-win10-i386 fail
> test-amd64-i386-xl-qemuu-win10-i386 fail
> test-amd64-amd64-qemuu-nested-intel pass
> test-amd64-amd64-xl-pvhv2-intel fail
> test-amd64-i386-qemuu-rhel6hvm-intel pass
> test-amd64-amd64-libvirt pass
> test-armhf-armhf-libvirt pass
> test-amd64-i386-libvirt pass
> test-amd64-amd64-xl-multivcpu pass
> test-armhf-armhf-xl-multivcpu pass
> test-amd64-amd64-pair pass
> test-amd64-i386-pair pass
> test-amd64-amd64-libvirt-pair pass
> test-amd64-i386-libvirt-pair pass
> test-amd64-amd64-amd64-pvgrub pass
> test-amd64-amd64-i386-pvgrub pass
> test-amd64-amd64-pygrub pass
> test-amd64-i386-libvirt-qcow2 fail
> test-amd64-amd64-xl-qcow2 pass
> test-armhf-armhf-libvirt-raw pass
> test-amd64-i386-xl-raw pass
> test-amd64-amd64-xl-rtds pass
> test-armhf-armhf-xl-rtds fail
> test-amd64-amd64-libvirt-vhd pass
> test-armhf-armhf-xl-vhd fail
>
>
> ------------------------------------------------------------
> 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
>
> broken-job build-armhf-pvops broken
>
> Not pushing.
>
> ------------------------------------------------------------
> commit b79708a8ed1b3d18bee67baeaf33b3fa529493e2
> Author: Anthony PERARD <anthony.perard@citrix.com>
> Date: Tue Oct 10 11:24:18 2017 +0100
>
> ui/gtk: Fix deprecation of vte_terminal_copy_clipboard
>
> vte_terminal_copy_clipboard() is deprecated in VTE 0.50.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> (cherry picked from commit 70857ad6212276dcda364e36b30258222bdb31bc)
>
> commit d957c46ff18d0d71809fd04fdc78700feacdc902
> Author: Roger Pau Monne <roger.pau@citrix.com>
> Date: Thu Aug 24 16:07:03 2017 +0100
>
> xen/pt: allow QEMU to request MSI unmasking at bind time
>
> When a MSI interrupt is bound to a guest using
> xc_domain_update_msi_irq (XEN_DOMCTL_bind_pt_irq) the interrupt is
> left masked by default.
>
> This causes problems with guests that first configure interrupts and
> clean the per-entry MSIX table mask bit and afterwards enable MSIX
> globally. In such scenario the Xen internal msixtbl handlers would not
> detect the unmasking of MSIX entries because vectors are not yet
> registered since MSIX is not enabled, and vectors would be left
> masked.
>
> Introduce a new flag in the gflags field to signal Xen whether a MSI
> interrupt should be unmasked after being bound.
>
> This also requires to track the mask register for MSI interrupts, so
> QEMU can also notify to Xen whether the MSI interrupt should be bound
> masked or unmasked
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> Reported-by: Andreas Kinzler <hfp@posteo.de>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
> (cherry picked from commit a8036336609d2e184fc3543a4c439c0ba7d7f3a2)
> Release-acked-by: Julien Grall <julien.grall@linaro.org>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-upstream-unstable test] 116118: FAIL
2017-11-13 11:52 ` Julien Grall
@ 2017-11-13 11:53 ` Wei Liu
2017-11-13 11:58 ` Julien Grall
0 siblings, 1 reply; 5+ messages in thread
From: Wei Liu @ 2017-11-13 11:53 UTC (permalink / raw)
To: Julien Grall
Cc: xen-devel, Wei Liu, Ian Jackson, osstest service owner,
Stefano Stabellini, Anthony Perard
On Mon, Nov 13, 2017 at 11:52:12AM +0000, Julien Grall wrote:
> Hi,
>
> On 11/13/2017 06:44 AM, osstest service owner wrote:
> > flight 116118 qemu-upstream-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/116118/
> >
> > Failures and problems with tests :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-armhf-pvops <job status> broken in 115713
> > build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
>
> Looking at the test result, build-armhf-pvops seems to have passed nicely
> the past few weeks but one time.
>
> So I am not sure why we are blocking here. Mostly the <job status> one.
host-install failure is probably not related to change in code. It is
trying to install a host to do test. In this case, to build kernel.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-upstream-unstable test] 116118: FAIL
2017-11-13 11:53 ` Wei Liu
@ 2017-11-13 11:58 ` Julien Grall
0 siblings, 0 replies; 5+ messages in thread
From: Julien Grall @ 2017-11-13 11:58 UTC (permalink / raw)
To: Wei Liu
Cc: Anthony Perard, Ian Jackson, xen-devel, Stefano Stabellini,
osstest service owner
Hi,
On 11/13/2017 11:53 AM, Wei Liu wrote:
> On Mon, Nov 13, 2017 at 11:52:12AM +0000, Julien Grall wrote:
>> Hi,
>>
>> On 11/13/2017 06:44 AM, osstest service owner wrote:
>>> flight 116118 qemu-upstream-unstable real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/116118/
>>>
>>> Failures and problems with tests :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> build-armhf-pvops <job status> broken in 115713
>>> build-armhf-pvops 4 host-install(4) broken in 115713 REGR. vs. 114457
>>
>> Looking at the test result, build-armhf-pvops seems to have passed nicely
>> the past few weeks but one time.
>>
>> So I am not sure why we are blocking here. Mostly the <job status> one.
>
> host-install failure is probably not related to change in code. It is
> trying to install a host to do test. In this case, to build kernel.
They have been failing with that for quite a while now. It looks like a
force push would be justified here. Any opinions?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-11-13 11:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-13 6:44 [qemu-upstream-unstable test] 116118: FAIL osstest service owner
2017-11-13 11:50 ` Anthony PERARD
2017-11-13 11:52 ` Julien Grall
2017-11-13 11:53 ` Wei Liu
2017-11-13 11:58 ` Julien Grall
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).