harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hindess <mark.hind...@googlemail.com>
Subject Re: Build failed in Hudson: Harmony-1.5-head-linux-x86_64 #696
Date Sun, 14 Mar 2010 07:14:37 GMT

In message <5899fca71003131235w5ae9e96anec0e962aa35e5f00@mail.gmail.com>,
Tim Ellison writes:
>
> On 13 March 2010 10:39, Mark Hindess <mark.hindess@googlemail.com> wrote:
> >
> > These build breaks were caused by my common_resources change.  I've
> > fixed that (by removing the reference to the old common_resources
> > checkout) but it highlights another problem.
> >
> > This hudson build can't create a correct workspace if the workspace
> > is deleted.  The reason is that it checks out the federated build to
> > harmony thus creating harmony/ working_classlib but this is not yet
> > "svn switch"ed to the real classlib tree.  Then it tries to check
> > out harmony/working_classlib with the real url but sees the already
> > svn checked out directory and refuses to overwrite it.
> >
> > The fix is to manually visit the workspace and "svn switch
> > working_*" to the appropriate urls.  I've done this for now.
> >
> > I think the only way to fix this and track the svn commits
> > is to checkout the working_* trees to, for example,
> > ignored/working_classlib and suffer the duplication.
> >
> > Tim, does that make sense?  I don't think we can have builds that
> > can't bootstrap their own workspace.
>
> Only to the extent that the whole switching thing makes sense.  Never
> liked that.

Let's discuss that.

> Anyway, I guess so, even though it seems a shame to take up so much
> unused space.

I've modified the builds to use 'ignored'.  Some were already using
'harmony/ignored' so I used that prefix although actually I think having
them outside the harmony tree might be more straightforward.

I also fixed the 'Harmony-1.5-head-linux-x86_64-full-tests' as this was
missing a call to populate-src so it couldn't bootstrap itself from a
wiped workspace either.

Regards,
 Mark.



Mime
View raw message