Hi Ian,
On 02/11/17 13:27, Ian Jackson wrote:
Julien Grall writes ("Re: Commit moratorium to staging"):
Thank you for the explanation. I agree with the force push to unblock
master (and other tree I mentioned).
I will force push all the affected trees, but in a reactive way
because I base each force push on a test report - so it won't be right
away for all of them.
osstest service owner writes ("[xen-unstable test] 115471: regressions - FAIL"):
flight 115471 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115471/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114644
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114644
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail REGR. vs. 114644
The above are justifiable as discussed, leaving no blockers.
version targeted for testing:
xen bb2c1a1cc98a22e2d4c14b18421aa7be6c2adf0d
So I have forced pushed that.
Thank you! With that, the tree is re-opened. I will go through my
backlog of Xen 4.10 and have a look whether they are suitable.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
