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 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@gmail.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@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@gmail.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
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.
I fixed it. A bit hackish, but okay in my opinion.
- a Monticello importer test.
I had a look at it but I could not understand what is wrong. Apparently a class is not looked up probably. Maybe we could do a screensharing to pair program...
Cheers, Alexandre
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@gmail.com wrote: 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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Sat, Oct 12, 2013 at 4:53 AM, Alexandre Bergel alexandre.bergel@me.comwrote:
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.
I fixed it. A bit hackish, but okay in my opinion.
Tx Alex.
- a Monticello importer test.
I had a look at it but I could not understand what is wrong. Apparently a class is not looked up probably. Maybe we could do a screensharing to pair program...
Cheers, Alexandre
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@gmail.com
wrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Fri, Oct 11, 2013 at 9:16 PM, Tudor Girba tudor@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.
I committed a correction for this failing test. Now the test is green and so is the build.
Usman
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@gmail.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Le 12 oct. 2013 à 21:27, Usman Bhatti a écrit :
On Fri, Oct 11, 2013 at 9:16 PM, Tudor Girba tudor@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.
I committed a correction for this failing test. Now the test is green and so is the build.
It's seems that this correction has broken other projects (like Orion), but I can't say what is broken this jenkins can't buid the image.
Can you please explain what you have modified or check on Orion and certainly also on Moose-On-The-Web and moose-latest-dev-extras why the images can't be built?
Thanks in advance. Anne
Usman
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@gmail.com wrote: 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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Sun, Oct 13, 2013 at 9:44 AM, Anne Etien anne.etien@univ-lille1.frwrote:
Le 12 oct. 2013 à 21:27, Usman Bhatti a écrit :
On Fri, Oct 11, 2013 at 9:16 PM, Tudor Girba tudor@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.
I committed a correction for this failing test. Now the test is green and so is the build.
It's seems that this correction has broken other projects (like Orion), but I can't say what is broken this jenkins can't buid the image.
The Orion job was failing because moose-latest-dev-4.8 job was renamed to moose-latest-dev-4.9 after the release of 4.8. Since Orion and other non-updated projects were pointing to the older, now non-existing job, thus these were failing. I updated all the failing job to point to the renamed job and now these are green.
Can you please explain what you have modified or check on Orion and certainly also on Moose**-On**-The**-Webhttps://ci.inria.fr/moose/job/Moose-On-The-Web/ and moose**-latest**-dev**-extrashttps://ci.inria.fr/moose/job/moose-latest-dev-extras/ why the images can't be built?
Thanks in advance. Anne
Usman
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@gmail.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks, a lot. Anne Le 13 oct. 2013 à 13:22, Usman Bhatti a écrit :
On Sun, Oct 13, 2013 at 9:44 AM, Anne Etien anne.etien@univ-lille1.fr wrote:
Le 12 oct. 2013 à 21:27, Usman Bhatti a écrit :
On Fri, Oct 11, 2013 at 9:16 PM, Tudor Girba tudor@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.
I committed a correction for this failing test. Now the test is green and so is the build.
It's seems that this correction has broken other projects (like Orion), but I can't say what is broken this jenkins can't buid the image.
The Orion job was failing because moose-latest-dev-4.8 job was renamed to moose-latest-dev-4.9 after the release of 4.8. Since Orion and other non-updated projects were pointing to the older, now non-existing job, thus these were failing. I updated all the failing job to point to the renamed job and now these are green.
Can you please explain what you have modified or check on Orion and certainly also on Moose-On-The-Web and moose-latest-dev-extras why the images can't be built?
Thanks in advance. Anne
Usman
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@gmail.com wrote: 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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Anne Etien -
Tudor Girba -
Usman Bhatti