[Pharo-project] [regression reporter]regression occurred
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 ...
oops... those are a lot of regressions :) 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 ...
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 ...
Le 16/04/2013 14:11, Marcus Denker a écrit :
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.
Who was asking if it wasn't a good idea to use Opal by default ? Markus, look, plenty of failed tests to help you progress :) Thierry
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 ...
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
These was because Destructive regression tests were loaded in the image. Should be fixed soon. 2013/4/16 Goubier Thierry <thierry.goubier@cea.fr>
Le 16/04/2013 14:11, Marcus Denker a écrit :
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.
Who was asking if it wasn't a good idea to use Opal by default ?
Markus, look, plenty of failed tests to help you progress :)
Thierry
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=linux/58/<https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=lin...>
71 regressions found. CompilerTests.**ClosureCompilerTest.**testBlockDoitDecompilation CompilerTests.**ClosureCompilerTest.**testDecompiledDoitMethodTempNa** mes CompilerTests.**ClosureCompilerTest.**testSourceRangeAccessForClosur** eBytecodeInjectInto CompilerTests.**ClosureCompilerTest.**testSourceRangeAccessForClosur** eLongFormBytecodeInjectInto CompilerTests.**ClosureCompilerTest.**testSourceRangeAccessForInject** Into 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.**testExpectedExpressionInBraceA* *rray CompilerTests.**CompilerNotifyingTest.**testExtraneousStatementAfterAR* *eturnInABlock CompilerTests.**CompilerNotifyingTest.**testInvalidRadix CompilerTests.**CompilerNotifyingTest.**testLiteralCharacterMissing ...
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
-- Clément Béra Mate Virtual Machine Engineer Bâtiment B 40, avenue Halley 59650 *Villeneuve d'Ascq*
it is already fixed :) On Apr 16, 2013, at 4:09 PM, Clément Bera <bera.clement@gmail.com> wrote:
These was because Destructive regression tests were loaded in the image. Should be fixed soon.
2013/4/16 Goubier Thierry <thierry.goubier@cea.fr> Le 16/04/2013 14:11, Marcus Denker a écrit :
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.
Who was asking if it wasn't a good idea to use Opal by default ?
Markus, look, plenty of failed tests to help you progress :)
Thierry
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 ...
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
-- Clément Béra Mate Virtual Machine Engineer Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
aaah I love to see a response to that :P my vicious plan to spam the pharo list when there are new tests failing seems to work :) On 2013-04-16, at 14:11, Marcus Denker <marcus.denker@inria.fr> wrote:
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 ...
participants (7)
-
Camillo Bruni -
Clément Bera -
Esteban Lorenzano -
Goubier Thierry -
Marcus Denker -
no-reply＠ci.inria.fr -
stephane ducasse