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@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@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."