On 07/06/18 13:58, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble:
> broken/fail/pass"):
>> Are you fine then to lift the current commit moratorium?
>
> That seems sensible, if you don't expect to be trying to bran
Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble:
broken/fail/pass"):
> Are you fine then to lift the current commit moratorium?
That seems sensible, if you don't expect to be trying to branch RSN
because of the save/rest
On 07/06/18 12:29, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble:
> broken/fail/pass"):
>> The same host (italia1) that had the failed xtf test yesterday. The two
>> failures are looking very similar to me.
>>
&
Juergen Gross writes ("Re: [Xen-devel] [xen-unstable test] 123831: trouble:
broken/fail/pass"):
> The same host (italia1) that had the failed xtf test yesterday. The two
> failures are looking very similar to me.
>
> Again the question: should we do a force push?
I th
On 07/06/18 03:55, osstest service owner wrote:
> flight 123831 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/123831/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>
flight 123831 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123831/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumprun-i386 broken
