On Apr 16, 2013, at 2:08 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
oops... those are a lot of regressions :)
This should not happen: This means that somehow Opal is taken as the compiler. (The tests are not compatible between the two, we are going through them one by one, either porting or fixing⦠but it takes while). If they fail this mean that the wrong compiler is used when running the tests.
On Apr 16, 2013, at 2:06 PM, no-reply@ci.inria.fr wrote:
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=lin...
71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...