On Sat, May 7, 2016 at 5:19 PM, Meng Xu wrote:
> On Tue, May 3, 2016 at 5:46 PM, Dario Faggioli
> wrote:
>>
>> The scheduling hooks API is now used properly, and no
>> initialization or de-initialization happen in
>> alloc/free_pdata any longer.
flight 93809 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93809/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93800 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93800/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93791 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93791/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
Hi Wei,
On Wed, May 4, 2016 at 12:04 PM, Wei Liu wrote:
>
> On Tue, May 03, 2016 at 11:46:27PM +0200, Dario Faggioli wrote:
> > Hi,
> >
> > This small series contains some bugfixes for various schedulers. They're all
> > bugfixes, so I think all should be considered for 4.7.
On Tue, May 3, 2016 at 5:46 PM, Dario Faggioli
wrote:
>
> The scheduling hooks API is now used properly, and no
> initialization or de-initialization happen in
> alloc/free_pdata any longer.
>
> In fact, just like it is for Credit2, there is no real
> need for
flight 93781 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93781/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
From: Paul Durrant
Date: Thu, 5 May 2016 12:19:28 +0100
> +struct xenvif_hash_cache {
> + rwlock_t lock;
You really don't want to lock on every SKB hash computation like
this, turn this into a spin lock for locking the write side and
use RCU locking for lookup and
flight 93772 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93772/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93765 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93765/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93756 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93756/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
On May 7, 2016 03:34, "Big Strong" wrote:
>>
>> libxc functions always return -1 when it fails. You need the specific
>> errno to know what went wrong.
>
>
> Yeah, I know it means a failure. Actually, I noticed that there is a
comment at the source code of xen, which says :
>
flight 93747 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93747/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
This run is configured for baseline tests only.
flight 44394 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44394/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 14
flight 93745 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93745/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93734 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93734/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
flight 93725 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93725/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-raw 7 host-ping-check-xen fail pass in 93638
flight 93731 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93731/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 14 guest-saverestore fail REGR. vs. 91479
flight 44395 distros-debian-stretch real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44395/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3863 host-install(3) broken
>
> libxc functions always return -1 when it fails. You need the specific
> errno to know what went wrong.
Yeah, I know it means a failure. Actually, I noticed that there is a
comment at the source code of xen
20 matches
Mail list logo