[Pharo-project] longer builds history
Hi, I extended the history of CI job Pharo 1.4 Tests-Unix to 60 builds/days. I wanted to find when testStWriter tests started to fail and the history was too short (7). This job takes 2MB so I hope it is not a problem. The two tests failures Graphics.Tests.Primitives.BitmapTest.testCompressToByteArrayIntegrity Graphics.Tests.Primitives.BitmapTest.testCompressToByteArraySize seem to be only accidental The tests Ring.Tests.Kernel.RGClassDefinitionTest.testWithComment Ring.Tests.Kernel.RGCommentDefinitionTest.testNewComment have a fix here: http://code.google.com/p/pharo/issues/detail?id=5507 Cheers, -- Pavel
On Sun, Mar 18, 2012 at 2:32 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I extended the history of CI job Pharo 1.4 Tests-Unix to 60 builds/days. I wanted to find when testStWriter tests started to fail and the history was too short (7). This job takes 2MB so I hope it is not a problem.
Using some old images I located the point where it started to fail. It was in update 14387, issue 5441 (http://code.google.com/p/pharo/issues/detail?id=5441) and in change of method ClassDefinition >> #printCategoryChunk:on:withStamp:priorMethod:
The two tests failures  Graphics.Tests.Primitives.BitmapTest.testCompressToByteArrayIntegrity  Graphics.Tests.Primitives.BitmapTest.testCompressToByteArraySize seem to be only accidental
The tests  Ring.Tests.Kernel.RGClassDefinitionTest.testWithComment  Ring.Tests.Kernel.RGCommentDefinitionTest.testNewComment have a fix here: http://code.google.com/p/pharo/issues/detail?id=5507
Cheers, -- Pavel
participants (1)
-
Pavel Krivanek