stephane ducasse wrote:
http://hudson.jooshr.org/job/Pharo1.1/81/
is it because the tests cannot run?
It builds and runs the tests now (with some failure reports).
In build#82, I saw in the stack trace some EOCD message, which usually
means some kind of package missing, corruption, or download problem. I
cleared the package-cache and got the same problem.
It was updating from PharoCore-1.1-11239-UNSTABLE, so I changed to the
latest: PharoCore-1.1-11254-UNSTABLE.1, and now the build/test works.
There probably were no updates to be applied to 11254, so of course the
build worked.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
