for 5) I fixed it. Stef
Little update!
Build is working now: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/
There are already some tests to fix:
CollectionsTests.Arrayed.FloatArrayTest.testArithmeticCoercion 0.0030 1 Metacello.TestsMC.MetacelloCurrentVersionTest.testFoo40Loaded1Package1LaterPackage 3.363 18 Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testBaselineFetch 0.059 18 Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testBaselineLoad 0.757 18 Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testIssue49PartialLoadC 1.506 18 Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testIssue49PartialLoadG 1.717 18 Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testIssue49PartialLoadC 1.62 18 Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testIssue49PartialLoadG 1.774 18 Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testBaselineLoad 0.828 18 Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testBaselineFetch 0.058 18 Metacello.TestsMC.MetacelloGoferFunctionalTest.testPackageResolution 0.011 18 Metacello.TestsMC.MetacelloGoferFunctionalTest.testComparison 0.0080 18 Metacello.TestsMC.MetacelloMCCachingLoaderTestCase.testBaselineLoad 0.963 18 Metacello.TestsMC.MetacelloMCSpecLoaderTest.testLatestPackage 0.016 18 Tests.Release.ReleaseTest.testObsoleteClasses 1.081 56 Refactoring.Tests.Core.RBInlineMethodFromComponentTest.testInlineEmptyComponentMethod 0.148 102 Tests.Release.ReleaseTest.testUndeclared
1) Most of them (actually 13 of 17), are from metacello and Gofer. Dale said he's going to replicate Gofer changes to squeak and gemstone, and fix the tests after that.
2) One is from the recently added Collections-Arithmetic. It's sending #clone instead of #copy.
3) testObsoleteClasses is fixed here (http://code.google.com/p/pharo/issues/detail?id=3681&q=testObsoleteClasses&c...). I will integrate it in a minutes.
4) testInlineEmptyComponentMethod is failing because there is an initialization method that is doing:
Refactoring class>>initializeRefactoringOptions RefactoringOptions := IdentityDictionary new. RefactoringOptions at: #implementorToInline put: [ :ref :imps | self error: #implementorToInline ];
at: #methodName put: [ :ref :methodName | self error: #methodName ];
at: #selfArgumentName put: [ :ref | self error: #selfArgumentName ];
at: #selectVariableToMoveTo put: [ :ref :class :selector | self error: #selectVariableToMoveTo ];
at: #variableTypes put: [ :ref :types :selected | self error: #variableTypes ];
at: #extractAssignment put: [ :ref :varName | self error: #extractAssignment ];
at: #inlineExpression put: [ :ref :string | self error: #inlineExpression ];
at: #alreadyDefined put: [ :ref :cls :selector | self error: #alreadyDefined ];
at: #useExistingMethod put: [ :ref :selector | self error: #useExistingMethod ];
at: #openBrowser put: [ :ref :env | self error: #openBrowser ]
And it breaks when the test is using that dictionary elements ;). Does someone know about it?
5) testUndeclared. Undeclared still has inside it #CustomMenu, #DefaultStubs, #KedamaFloatArray. #CustomMenu is fixed (http://code.google.com/p/pharo/issues/detail?id=3712&q=CustomMenu&colspec=ID...). I'll integrate it in a while. #DefaultStubs remains to be fixed: (http://code.google.com/p/pharo/issues/detail?id=3711&q=DefaultStubs&colspec=...) #KedamaFloatArray is referenced in WordArray #+, #-, #*, #=. Should it be referencing to FloatArray instead? :P. It's a change for Collection-Arithmetic.
Any clue about unresolved tasks?
Thanks! Guille