16 Mar
2010
16 Mar
'10
8:45 p.m.
If it's moose algos, than just load the latest version manually.
Doru
Sent from my iPhone
On Mar 16, 2010, at 21:37, Alexandre Bergel <alexandre(a)bergel.eu> wrote:
Simon, do you know which test I should exclude?
I am currently conducting an experiment on Moose unit test, and the
deadline is approaching. Naturally, I could use an old version of
Moose, but I do not think this is the idea.
Cheers,
Alexandre
On 16 Mar 2010, at 07:52, Simon Denier wrote:
On 16 mars 2010, at 13:34, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I also tried to load it in RC3. I somehow managed
(loadDefault
does not seem to do the job).
But I couldn't run the test. They block after a while.
Yep, that's because old package versions from MooseAlgos got
loaded, including the one with a wrong recursive behavior which
launch an infinite loop.
Cheers,
Alexandre
On 16 Mar 2010, at 06:51, Simon Denier wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Did anyone manage to load a clean Moose in Pharo 1.0 RC3?
I tried to load ConfigurationOfPharo first, then Moose, but it
looks like it loads some old packages even if I perform
loadDefault.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev