[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-4.0-testing test] 13683: regressions - trouble: blocked/broken/fail/pass



Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 13683: regressions 
- trouble: blocked/broken/fail/pass"):
> +QEMU_TAG ?= d7d453f51459b591faa96d1c123b5bfff7c5b6b6
> +# Thu Sep 6 17:05:30 2012 +0100
> +# Disable qemu monitor by default.  The qemu monitor is an overly
>  
> 
> But d7.... is a commit in qemu-xen-4.1-testing.git. The correct commit
> in qemu-xen-4.0-testing.git is eaa1bd612f50d2f253738ed19e14981e4ede98a5.

This is my fault.  My shonky script for updating these (which I was
editing yesterday) had a bug that meant it always used the current
branch of my source git repo rather than the right branch, for finding
the tag value (although it would push the correcct thing).  I have
fixed it.

It seems that only 4.0 was affected.

> Not sure why it didn't fail when cloning this repo -- I guess it was
> actually able to resolve the 4.1-testing commit, but then failed to
> build it...

These repos tend to have a lot of surplus commits in because they all
have all the tags.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.