On Tue, Aug 7, 2012 at 10:37 AM, Mariano Martinez Peck
<marianopeck@gmail.com> wrote:
On Tue, Aug 7, 2012 at 10:32 AM, Pavel Krivanek
<pavel.krivanek@gmail.com> wrote:
We are starting to have a lot of failing tests again
CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNames
CompressionTests.Archive.ZipArchiveTest.testZip
FileSystem.Tests.Disk.DiskFileSystemTest.testEntryAt
FileSystem.Tests.Memory.MemoryFileSystemTest.testEntryAt
KernelTests.Chronology.StopwatchTest.testSingleTiming
KernelTests.Chronology.StopwatchTest.testStartStop
KernelTests.Chronology.TimeStampTest.testComparing
KernelTests.Chronology.TimeStampTest.testSorting
Zinc.Tests.ZnLogSupportTests.testLogEvent
RPackage.Tests.RPackageWithDoTest.testInvariant
Tests.Release.ReleaseTest.testMethodsWithUnboundGlobals
Tests.Release.ReleaseTest.testUndeclared
I think that we have to upgrade the monkey checking to stop such regressions...
Shouldn't Jenkins help us here?
We have about three options:
1) use Jenkins for updates checking
� � - maybe it was the original plan but it doesn't work because we do not want to rollback updates
2) create a fake update server and create Jenkins jobs that will check the updates and will not pass the dirty ones to mainstream
3) improve the Monkey do do more checks on fixes of issues - to run more tests etc. And do not allow fixes that do not pass.
The current state when we do not rollback updates and have poor issues checking may seem to look good for the fast development of the system with big radical changes but in reality it ends in state when if somebody wants to improve something he firstly has to fix things that started to be broken.
-- Pavel
�
--
Mariano
http://marianopeck.wordpress.com