|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
Test time on 3.9 branchHi All,
Should I really expect the tests to take an hour to run on Windows? Total: 3825 tests, 0 failures, 0 errors in 56 minutes 49.469 seconds. As you can see, no errors or failures were reported. However, there were some error-ish messages interspersed in the test output. Is this to be expected? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branchOn Mon, Nov 2, 2009 at 7:34 AM, Chris Withers <chris@...> wrote:
> Hi All, > > Should I really expect the tests to take an hour to run on Windows? Yes. > > Total: 3825 tests, 0 failures, 0 errors in 56 minutes 49.469 seconds. > > As you can see, no errors or failures were reported. Cool. > However, there were > some error-ish messages interspersed in the test output. Is this to be > expected? You didn't show the extra output, so I can't say. I wouldn't be surprised. Jim -- Jim Fulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branchJim Fulton wrote:
>> Should I really expect the tests to take an hour to run on Windows? > > Yes. Erk. Is there a subset I can look to run when looking to patch the ZEOStorage308Adapter? >> However, there were >> some error-ish messages interspersed in the test output. Is this to be >> expected? > > You didn't show the extra output, so I can't say. I wouldn't be surprised. Here's the full output... cheers, Chris Running .!no tests here! tests: Set up .!no tests here! in 0.016 seconds. Ran 1 tests with 0 failures and 0 errors in 0.000 seconds. Running .BlobAdaptedFileStorageBlobTests tests: Tear down .!no tests here! in 0.000 seconds. Set up .BlobAdaptedFileStorageBlobTests in 0.000 seconds. Ran 87 tests with 0 failures and 0 errors in 18.062 seconds. Running .BlobAdaptedFileStorageTests tests: Tear down .BlobAdaptedFileStorageBlobTests in 0.000 seconds. Set up .BlobAdaptedFileStorageTests in 0.000 seconds. error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:21997 at 0x11205a8> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:27769 at 0x11205a8> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event Ran 107 tests with 0 failures and 0 errors in 9 minutes 29.578 seconds. Running .BlobFileStorageBlobTests tests: Tear down .BlobAdaptedFileStorageTests in 0.000 seconds. Set up .BlobFileStorageBlobTests in 0.000 seconds. Ran 87 tests with 0 failures and 0 errors in 16.563 seconds. Running .BlobWritableCacheTests tests: Tear down .BlobFileStorageBlobTests in 0.000 seconds. Set up .BlobWritableCacheTests in 0.000 seconds. error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:23335 at 0x11225a8> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:24274 at 0x11225a8> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event Ran 106 tests with 0 failures and 0 errors in 9 minutes 12.500 seconds. Running .ClientStorageNonSharedBlobsBlobTests tests: Tear down .BlobWritableCacheTests in 0.015 seconds. Set up .ClientStorageNonSharedBlobsBlobTests in 0.016 seconds. Ran 73 tests with 0 failures and 0 errors in 1 minutes 20.750 seconds. Running .ClientStorageSharedBlobsBlobTests tests: Tear down .ClientStorageNonSharedBlobsBlobTests in 0.031 seconds. Set up .ClientStorageSharedBlobsBlobTests in 0.000 seconds. Ran 73 tests with 0 failures and 0 errors in 1 minutes 23.734 seconds. Running .DemoStorageTests tests: Tear down .ClientStorageSharedBlobsBlobTests in 0.015 seconds. Set up .DemoStorageTests in 0.000 seconds. Ran 50 tests with 0 failures and 0 errors in 4 minutes 16.000 seconds. Running .FileStorageTests tests: Tear down .DemoStorageTests in 0.000 seconds. Set up .FileStorageTests in 0.000 seconds. error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:25849 at 0x110bc88> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:22951 at 0x110bc88> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'Data.fs' [C:\P ython26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoser ver.py|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\Fi leStorage.py|cleanup|1314]) warning: unhandled close event Ran 102 tests with 0 failures and 0 errors in 8 minutes 54.312 seconds. Running .MVCCMappingBlobTests tests: Tear down .FileStorageTests in 0.015 seconds. Set up .MVCCMappingBlobTests in 0.000 seconds. Ran 68 tests with 0 failures and 0 errors in 5.312 seconds. Running .MappingStorageTests tests: Tear down .MVCCMappingBlobTests in 0.000 seconds. Set up .MappingStorageTests in 0.000 seconds. Ran 51 tests with 0 failures and 0 errors in 4 minutes 28.609 seconds. Running .ZEO Connection Tests tests: Tear down .MappingStorageTests in 0.063 seconds. Set up .ZEO Connection Tests in 0.015 seconds. Ran 64 tests with 0 failures and 0 errors in 6 minutes 4.985 seconds. Running .testZeo-misc tests: Tear down .ZEO Connection Tests in 0.000 seconds. Set up .testZeo-misc in 0.000 seconds. error: uncaptured python exception, closing channel <__main__.ZEOTestServer localhost:22555 at 0x112bf30> (<type 'exception s.WindowsError'>:[Error 32] The process cannot access the file because it is being used by another process: 'fs' [C:\Python 26\lib\asyncore.py|read|74] [C:\Python26\lib\asyncore.py|handle_read_event|408] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.p y|handle_accept|97] [c:\localsvn\zodb\src\ZEO\tests\zeoserver.py|cleanup|34] [c:\localsvn\zodb\src\ZODB\FileStorage\FileSto rage.py|cleanup|1314]) warning: unhandled close event Ran 36 tests with 0 failures and 0 errors in 4 minutes 31.906 seconds. Running zope.testing.testrunner.layer.UnitTests tests: Tear down .testZeo-misc in 0.000 seconds. Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. C:\Python26\lib\unittest.py:336: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - int erpreting them as being unequal callableObj(*args, **kwargs) Ran 2920 tests with 0 failures and 0 errors in 6 minutes 25.422 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Total: 3825 tests, 0 failures, 0 errors in 56 minutes 49.469 seconds.-- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branchOn Mon, Nov 2, 2009 at 7:44 AM, Chris Withers <chris@...> wrote:
> Jim Fulton wrote: >>> >>> Should I really expect the tests to take an hour to run on Windows? >> >> Yes. > > Erk. Is there a subset I can look to run when looking to patch the > ZEOStorage308Adapter? No. Feel my windows pain. >>> However, there were >>> some error-ish messages interspersed in the test output. Is this to be >>> expected? >> >> You didn't show the extra output, so I can't say. I wouldn't be surprised. > > Here's the full output... Yeah, that's normal. Jim -- Jim Fulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branch - windows?Jim Fulton wrote:
>>>> Should I really expect the tests to take an hour to run on Windows? >>> Yes. >> Erk. Is there a subset I can look to run when looking to patch the >> ZEOStorage308Adapter? > > Feel my windows pain. Do the tests take much less time to run on Linux? If so, any idea as to why? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branch - windows?On 11/02/2009 12:59 PM, Chris Withers wrote:
> Jim Fulton wrote: >>>>> Should I really expect the tests to take an hour to run on Windows? >>>> Yes. >>> Erk. Is there a subset I can look to run when looking to patch the >>> ZEOStorage308Adapter? >> >> Feel my windows pain. > > Do the tests take much less time to run on Linux? > If so, any idea as to why? I remember running them in less than 20 minutes. -- Christian Theune · ct@... gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
|
|
Re: Test time on 3.9 branch - windows?On Mon, Nov 2, 2009 at 6:59 AM, Chris Withers <chris@...> wrote:
> Jim Fulton wrote: >>>>> >>>>> Should I really expect the tests to take an hour to run on Windows? >>>> >>>> Yes. >>> >>> Erk. Is there a subset I can look to run when looking to patch the >>> ZEOStorage308Adapter? >> >> Feel my windows pain. > > Do the tests take much less time to run on Linux? Yes. On the order of 15 minutes. > If so, any idea as to why? Process start up is very slow on windows. Jim -- Jim Fulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@... https://mail.zope.org/mailman/listinfo/zodb-dev |
| Free embeddable forum powered by Nabble | Forum Help |