broken build (Was: /hg/icedtea6: 6 new changesets)

[Mark Wielaard]

On Thu, 2010-07-29 at 21:55 +0100, Dr Andrew John Hughes wrote:
> On 14:34 Thu 29 Jul     , Omair Majid wrote:
> > > That seems right, given the circumstances.  The question is how you
> > > got into a state where there was a conflict to begin with.
> > >
> > 
> > Hm... 'hg view' shows what might have happened. Apparently mjw had an 
> > old checkout lying around (missing hg pull && hg update perhaps?).
> > 
> 
> I haven't checked that.  My hg view segfaults, due to tcl not liking gcc 4.5:
> 
> $ hg view
> *** buffer overflow detected ***: wish terminated

It works on my machine, and it is useful to see what seemed to have
happened. I still don't understand how that can have be. But apparently
I did my commit and then the merge against something really old :{

> > > Note that you can check what will be pushed with 'hg in'.
> > 
> > Shouldnt that be 'hg out'? IIRC 'in' (or incoming) checks for the 
> > changesets that would get pulled in on hg pull
> > 
> 
> Yeah, typo.  hg in is useful too though! :-)

Wish I had used that before pushing. hg outgoing is what would have
shown me something odd was going on before a push.

> > > There don't seem to be any problems building anyway.
> > 
> > Yup, I can confirm. Even though there are tons of files listed, they 
> > seem to refer to stuff that was merged. The build works just fine.

Sadly it seems something did break. The auto-builder just informed me:
http://icedtea.classpath.org/pipermail/testresults/2010-July/000672.html

It only seems to impact older setups that trigger the QNAME workaround
patch. I cannot immediately see how my commit/merge broke that. But will
try to fix it tomorrow. Slightly scared my fix/merging will make it
worse though. So first some sleep to get a clear head.

Cheers,

Mark