22 Feb
2011
22 Feb
'11
8:59 p.m.
Hi!
Today we have 4 yellow test methods:
- MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is fixed by now
- MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in
configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But,
how comes that the menu of famix classes contains a smalldude action? Apparently, the
small dude actions are defined outside smalldude. The method viewDuplicationComplexity is
defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose
package?
- MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
- MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to
'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core
packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
See
<http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
22 Feb
22 Feb
9:13 p.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
Alex, as I wrote before, these tests fail because SmallDude and DSM are not in
ConfigurationOfMoose.
This in turn happens because when they are included, we end up looping while loading.
Cheers,
Doru
On 22 Feb 2011, at 20:59, Alexandre Bergel wrote:
Hi!
Today we have 4 yellow test methods:
- MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is fixed by now
- MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in
configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But,
how comes that the menu of famix classes contains a smalldude action? Apparently, the
small dude actions are defined outside smalldude. The method viewDuplicationComplexity is
defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose
package?
- MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
- MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to
'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core
packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
See
<http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
9:21 p.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
Doru, I know this. But do you find normal that some tests turn yellow by simply removing
SmallDude and DSM?
Alexandre
On 22 Feb 2011, at 17:13, Tudor Girba wrote:
Alex, as I wrote before, these tests fail because
SmallDude and DSM are not in ConfigurationOfMoose.
This in turn happens because when they are included, we end up looping while loading.
Cheers,
Doru
On 22 Feb 2011, at 20:59, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Today we have 4 yellow test methods:
- MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is fixed by now
- MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in
configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But,
how comes that the menu of famix classes contains a smalldude action? Apparently, the
small dude actions are defined outside smalldude. The method viewDuplicationComplexity is
defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose
package?
- MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
- MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to
'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core
packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev See
<http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
9:28 p.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
No, but I just mentioned where the code was :)
Doru
On 22 Feb 2011, at 21:21, Alexandre Bergel wrote:
Doru, I know this. But do you find normal that some
tests turn yellow by simply removing SmallDude and DSM?
Alexandre
On 22 Feb 2011, at 17:13, Tudor Girba wrote:
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
Alex, as I wrote before, these tests fail because
SmallDude and DSM are not in ConfigurationOfMoose.
This in turn happens because when they are included, we end up looping while loading.
Cheers,
Doru
On 22 Feb 2011, at 20:59, 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 Hi!
Today we have 4 yellow test methods:
- MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is fixed by now
- MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in
configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But,
how comes that the menu of famix classes contains a smalldude action? Apparently, the
small dude actions are defined outside smalldude. The method viewDuplicationComplexity is
defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose
package?
- MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
- MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to
'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core
packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev See
<http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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 
10:01 p.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
Hi,
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> Today we have 4 yellow test methods:
>>>
>>> - MOEaselTest.testExamplesAreOkay is entirely my fault and the situation is
fixed by now
>>>
>>> - MooseFinderTest.testMenuEntriesForClasses is due to the missing dep in
configurationOfMoose. the method #allDuplications is invoked on a FAMIXClassGroup. But,
how comes that the menu of famix classes contains a smalldude action? Apparently, the
small dude actions are defined outside smalldude. The method viewDuplicationComplexity is
defined in Moose-MondrianPainting. Shall I move this method to the SmallDude-Moose
package?
>>>
>>> - MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
I do not understand, CycleTable is my work, and I am not sure to have written this kind of
test.
>>>
>>> - MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference
to 'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use
core packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
You are right. I wrote the tests based on DSM. Now, Category-Importer does not make sense
anymore because of RPackage and we should remove it (there is a bug entry).
So you can also remove this test.
Jannik
Cheers,
Alexandre
On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:10 p.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
>>> -
MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
I do not understand, CycleTable is my work, and I am not sure to have written this kind
of test. >>> -
MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference to
'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use core
packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
You are right. I wrote the tests based on DSM. Now, Category-Importer does not make sense
anymore because of RPackage and we should remove it (there is a bug entry).
So you can also remove this test.
Jannik
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
> Cheers,
> Alexandre
>
>
>
> On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
>
>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
>>
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> 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
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
_______________________________________________
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 
23 Feb
23 Feb
10:07 a.m.
New subject: Hudson build is still unstable: moose-latest-dev #209
On 22 févr. 2011, at 22:10, Alexandre Bergel wrote:
Ah ah! Your signed the MIT license don't you, so be ready to see the world use your
work!
More seriously, testMenuEntriesForPackages is a test I wrote that try all the menu entry
you may get when you right click on the moose panel. viewDependenciesWithCycles raises an
error. Nothing abnormal since DSM is not installed. But my question is why this menu item
is present, if DSM is not loaded.
Probably a menu item is ill-placed? CycleTable (at least the original one I wrote, upon
which Jannik's DSMCycleTable is built) used to be in Moose-MondrianPaintings.
MOCircularColors is referenced in FamixPackageGroup>>viewDependenciesWithCyclesOn:
(a small basic viz which draw a graph) which is still in Moose-MondrianPaintings.
Now CycleTable and MOCircularColors have been moved to the package Moose-CycleTable.
MOCircularColors should be integrated in Mondrian.
No problem to do so, but I would like to understand a bit more why. I though that
RPackage is a replacement for PackageInfo. How does it interfere with class categories?
Alexandre
--
Simon Denier
>>> -
MooseFinderTest.testMenuEntriesForPackages revealed that the method
#viewDependenciesWithCycles makes a reference to MOCircularColors, which is not present.
According to a few days old version of moose, this class belongs to the package
Moose-CycleTable. Doru, an idea what happened here?
I do not understand, CycleTable is my work, and I am not sure to have written this kind
of test.
>>> - MooseSqueakClassPackageImporterTest.testCategoryImporter makes a reference
to 'Moose-TestResources-Dsm*', which is odd. It should not. Maybe we could use
core packages for this tests. The test is simple, it should be easy to fix. Shall I do it?
You are right. I wrote the tests based on DSM. Now, Category-Importer does not make sense
anymore because of RPackage and we should remove it (there is a bug entry).
So you can also remove this test.
Jannik
_______________________________________________
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 >>
>> Cheers,
>> Alexandre
>>
>>
>>
>> On 22 Feb 2011, at 06:14, admin(a)moosetechnology.org wrote:
>>
>>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/209/>
>>>
>>>
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> 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
>
> --
> www.tudorgirba.com
>
> "The coherence of a trip is given by the clearness of the goal."
>
>
>
>
>
> _______________________________________________
> 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
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4811
days inactive
4812
days old
6 comments
4 participants
participants (4)
-
Alexandre Bergel -
jannik.laval -
Simon Denier -
Tudor Girba