Build failed in Hudson: Pharo 1.2 #114

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Build failed in Hudson: Pharo 1.2 #114

Torsten Bergmann
It worked for me since the MCZ was already
in the package-cache. After I deleted the cache
I was able to reproduce the failure.

I've looked into it and it should now work.
The fix is in ConfigurationOfOmniBrowser-tbn.95.mcz
which now points to the correct repo.

Maybe Guillermo didnt notice the problem yesterday
since the version was in his cache too.
When switching repos in configs we should always
clean our local cache when testing.

At least it works here after cleaning the cache -
so please Marcus start a new build run...

Thx
T.
--
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Reply | Threaded
Open this post in threaded view
|

Re: Build failed in Hudson: Pharo 1.2 #114

Marcus Denker-4

On Feb 3, 2011, at 12:50 PM, Torsten Bergmann wrote:

> It worked for me since the MCZ was already
> in the package-cache. After I deleted the cache
> I was able to reproduce the failure.
>
> I've looked into it and it should now work.
> The fix is in ConfigurationOfOmniBrowser-tbn.95.mcz
> which now points to the correct repo.
>
> Maybe Guillermo didnt notice the problem yesterday
> since the version was in his cache too.
> When switching repos in configs we should always
> clean our local cache when testing.
>

I wonder why we don't just add one big global cache
on Amazon S3 for all packages?

> At least it works here after cleaning the cache -
> so please Marcus start a new build run...
>

Started.


--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.