[Xen-devel] [xen-unstable baseline-only test] 75183: trouble: blocked/broken

2018-09-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 75183 xen-unstable real [real] http://osstest.xensource.com/osstest/logs/75183/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64

[Xen-devel] [xen-unstable test] 127407: tolerable FAIL - PUSHED

2018-09-08 Thread osstest service owner
flight 127407 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/127407/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 127369 test-armhf-armhf-libvirt 14 save

[Xen-devel] [linux-linus test] 127403: regressions - FAIL

2018-09-08 Thread osstest service owner
flight 127403 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/127403/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 125898

[Xen-devel] [distros-debian-stretch test] 75180: trouble: blocked/broken

2018-09-08 Thread Platform Team regression test user
flight 75180 distros-debian-stretch real [real] http://osstest.xensource.com/osstest/logs/75180/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken build-i386

[Xen-devel] [linux-linus bisection] complete test-amd64-amd64-xl-qemuu-ovmf-amd64

2018-09-08 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job test-amd64-amd64-xl-qemuu-ovmf-amd64 testid debian-hvm-install Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/qemu-

[Xen-devel] [ovmf baseline-only test] 75178: trouble: blocked/broken

2018-09-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 75178 ovmf real [real] http://osstest.xensource.com/osstest/logs/75178/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm

[Xen-devel] [xen-unstable test] 127396: regressions - trouble: broken/fail/pass

2018-09-08 Thread osstest service owner
flight 127396 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/127396/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xen-freebsd broken test-armhf-armhf-xl-credit2

[Xen-devel] [libvirt test] 127401: regressions - FAIL

2018-09-08 Thread osstest service owner
flight 127401 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/127401/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt6 libvirt-buildfail REGR. vs. 123814 build-amd64-libvirt

[Xen-devel] [xen-unstable baseline-only test] 75174: trouble: blocked/broken

2018-09-08 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 75174 xen-unstable real [real] http://osstest.xensource.com/osstest/logs/75174/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64

[Xen-devel] [linux-linus test] 127389: regressions - FAIL

2018-09-08 Thread osstest service owner
flight 127389 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/127389/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 125898

Re: [Xen-devel] [DRBD-user] [PATCH] xen-blkback: Switch to closed state after releasing the backing device

2018-09-08 Thread Valentin Vidic
On Fri, Sep 07, 2018 at 07:14:59PM +0200, Valentin Vidic wrote: > In fact the first one is the original code path before I modified > blkback. The problem is it gets executed async from workqueue so > it might not always run before the call to drbdadm secondary. As the DRBD device gets released o