[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [qemu-upstream-unstable test] 22066: regressions - FAIL
On Sat, 2013-11-23 at 00:50 +0100, Sander Eikelenboom wrote: > Thursday, November 21, 2013, 6:44:35 PM, you wrote: > > > On Thu, 2013-11-21 at 18:36 +0100, Sander Eikelenboom wrote: > >> Thursday, November 21, 2013, 5:37:57 PM, you wrote: > >> > >> > flight 22066 qemu-upstream-unstable real [real] > >> > http://www.chiark.greenend.org.uk/~xensrcts/logs/22066/ > >> > >> > Regressions :-( > >> > >> > Tests which did not succeed and are blocking, > >> > including tests which could not be run: > >> > test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. > >> > vs. 20054 > >> > >> Wasn't this supposed to be fixed by Anthony Perards fix for Xen ? > > > Yes, but that needs to pass regression testing on the xen-unstable > > branch before the qemu branch will be tested against it. xen-unstable is > > currently not going through for unrelated reasons but I expect it will > > unwedge tonight. > > > Ian. > > > > Hi Ian / Stefano, > > Is the tree and branch being tested here published somewhere ? All of the details are in each test pass/failure report. Follow the URL and click on one of the column headers. http://www.chiark.greenend.org.uk/~xensrcts/logs/22066/ => http://www.chiark.greenend.org.uk/~xensrcts/logs/22066/build-amd64/info.html => tree_qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git > A commit of mine is in there, but i can't find it where i would expected in: Where is "there"? > > git://xenbits.xen.org/staging/qemu-upstream-unstable.git > > (and also not in: git://xenbits.xen.org/qemu-upstream-unstable.git > nor git://git.qemu.org/qemu.git) > > > But it is mentioned in the "People who touched revisions under test" ... The 1.6 merge was big -- are you sure you looked far enough back? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |