11 Oct
2013
11 Oct
'13
9:23 p.m.
As soon as the tests are green, and we fix the ugly tiny bug with the
splitters in tables (
http://code.google.com/p/moose-technology/issues/detail?id=985), we release
4.9 and move to Moose 5.0 on Pharo 3.0. I think this can happen in a few
days if we work on it.
Doru
On Fri, Oct 11, 2013 at 9:16 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Moose is actually not unstable at all, but the tests
did look bad.
It was on my to do list to clean the tests. Now, I managed to:
- remove OSProcess from the executed tests
- remove references to Mondrian which is why most of the other tests failed
- fixed one Roassal test by adding a dummy ROGraphvizLayout>>doExecute:
(note that the graphviz layout is only loaded in the moose image, not
directly from Roassal).
Now, we only get 2 tests failing:
- Still a Roassal test related to the Steping behavior of the Graphviz
layout. I do not quite understand how to fix this one.
- a Monticello importer test.
It would be great if anyone could look into these two.
Cheers,
Doru
On Fri, Oct 11, 2013 at 5:31 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
There are several tests failing in Moose 4.9. Majority of them are
related to OSProcess and some others are related to Moose and Roassal. We
have Pharo sprint next week so, here in Lille, we can work on making
unstable builds on the moose jenkins green (Moose 4.9, Moose-algos, and
Moose-on-the-web). Because, it will be difficult for us to move the
downstream projects to Moose 4.9 unless the build is stable.
It would be good to know the roadmap to move to Pharo 3.0 because the
major change between Moose 4.8 and Moose 4.9 is removing Mondrian. So when
do we move to Pharo 3.0?
regards,
Usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"