Re: [Zope3-Users] Self-updating components?
Alec Munro <[EMAIL PROTECTED]> wrote: > Hi List, > > I'm finally getting into the swing of Zope 3 development, and I've > been doing a bit of thinking on how to integrate everything with > Subversion. > The general process I've settled on is as follows (this is all > happening on a development server): > > 1.SVN Update Code locally > 2.Edit Code > 3.Test Code on local Zope > 4.SVN Check-in Code from local > 5.SVN Check-out/Update code on development server > 6.Test Code on development Zope > 1.If successful, restart development Zope. > 2.If unsuccessful? IMO it's better to do: 1. SVN Update Code locally 2. Edit Code 3. Test Code on local Zope 4. Rsync code to development server 5. Test Code on development Zope 6. SVN Update local Zope to merge changes that happened meanwhile 7. If there were changes, goto 3 8. Check-in code from local You don't want to checkin code that ends up being wrong. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] problems with installation of zope3
[gf <[EMAIL PROTECTED]>] > Thanks for the response. I did google (and searched the list archives) > for previous similar errors, but apparently didn't try the right words > (I found a lot of OSX issues that seemed similar). > > In any case, I just reinstalled as an 'ordinary' user, ran 'make > check', and had what look to be similar errors (although there are now > more of them). If it wasn't clear, I was talking specifically (and only) about the one test I quoted: >>> FAIL: testUmask (zdaemon.tests.testzdrun.ZDaemonTests) >>> -- >>> Traceback (most recent call last): >>> File >>> "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", >>> line 244, in testUmask >>>self.assert_(not os.access(path, os.W_OK)) >>> File "/usr/lib/python2.3/unittest.py", line 278, in failUnless >>>if not expr: raise self.failureException, msg >>> AssertionError If that failure in testUmask went away, then you accomplished all I hoped to accomplish by not running as root. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] problems with installation of zope3
Thanks for the response. I did google (and searched the list archives) for previous similar errors, but apparently didn't try the right words (I found a lot of OSX issues that seemed similar). In any case, I just reinstalled as an 'ordinary' user, ran 'make check', and had what look to be similar errors (although there are now more of them). -g [snip: many errors] == ERROR: checkReadMethods (ZEO.tests.testZEO.MappingStorageTests) -- Traceback (most recent call last): File "/home/storage/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZEO/tests/testZEO.py", line 136, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes -- Ran 3970 tests in 392.115s FAILED (errors=24) make: *** [check] Error 1 On 7/20/05, Tim Peters <[EMAIL PROTECTED]> wrote: > [gf <[EMAIL PROTECTED]>] > ... > > FAIL: testUmask (zdaemon.tests.testzdrun.ZDaemonTests) > > -- > > Traceback (most recent call last): > > File > > "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", > > line 244, in testUmask > >self.assert_(not os.access(path, os.W_OK)) > > File "/usr/lib/python2.3/unittest.py", line 278, in failUnless > >if not expr: raise self.failureException, msg > > AssertionError > > Each time this one has been reported in the past, turned out the tests > were being run as root. Were you running as root? If so, don't. > ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] problems with installation of zope3
[gf <[EMAIL PROTECTED]>] ... > FAIL: testUmask (zdaemon.tests.testzdrun.ZDaemonTests) > -- > Traceback (most recent call last): > File > "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", > line 244, in testUmask >self.assert_(not os.access(path, os.W_OK)) > File "/usr/lib/python2.3/unittest.py", line 278, in failUnless >if not expr: raise self.failureException, msg > AssertionError Each time this one has been reported in the past, turned out the tests were being run as root. Were you running as root? If so, don't. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Self-updating components?
Hi List, I'm finally getting into the swing of Zope 3 development, and I've been doing a bit of thinking on how to integrate everything with Subversion. The general process I've settled on is as follows (this is all happening on a development server): 1.SVN Update Code locally 2.Edit Code 3.Test Code on local Zope 4.SVN Check-in Code from local 5.SVN Check-out/Update code on development server 6.Test Code on development Zope 1.If successful, restart development Zope. 2.If unsuccessful? The problem I have is how to automate steps 5 and on. I could put hooks into Subversion, but without some tricks, it seems like it would result in a lot of processing and restarts on the development server. Another idea I had, and the one that intrigues me the most at the moment, is making each component capable of updating itself. I really have no idea how it should work, if it's at all feasible, or advisable. Any hints or suggestions on this? ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] problems with installation of zope3
On Wed, 2005-07-20 at 09:09 -0600, gf wrote: > Hi, > I just downloaded zope3 ( ZopeX3-3.0.0.tar.gz) and issued the > 'configure', and 'make' commands. When I try a 'make check', I get > multiple errors (see bottom of message). > I am including below the output from what I think are relevant commands. > > I'd appreciate any help you can provide in diagnosing these errors. Is this relevant? http://www.zope.org/Collectors/Zope/1334 again, this may or may not lead you to a hint: http://zopewiki.org/HowToRunZopeUnitTests/src If you google the "OSError: [Errno 10] No child processes" you'll find more references to Python 2.3.4 and that error... But, my suggestion is to install Python 2.3.5 and Zope 3.1.0b unless you have some burning reason to install the experimental version. Cheers, -- Tim Cook, Consultant CHASE Health Informatics, Inc. GPG Key is on key servers everywhere. signature.asc Description: This is a digitally signed message part ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] problems with installation of zope3
Hi, I just downloaded zope3 ( ZopeX3-3.0.0.tar.gz) and issued the 'configure', and 'make' commands. When I try a 'make check', I get multiple errors (see bottom of message). I am including below the output from what I think are relevant commands. I'd appreciate any help you can provide in diagnosing these errors. -g --- $: uname -a Linux xxx 2.6.9-11-rfs #1 Tue Jun 14 08:27:18 MDT 2005 i686 i686 i386 GNU/Linux --- $: ./configure Configuring Zope X3 installation Testing for an acceptable Python interpreter... Python version 2.3.3 found at /usr/local/bin/python Python version 2.3.3 found at /usr/local/bin/python2.3 Python version 2.3.4 found at /usr/bin/python The optimum Python version (2.3.4) was found at /usr/bin/python. --- $: make check /usr/bin/python install.py -q build /usr/bin/python test.py -v Running UNIT tests at level 1 Running UNIT tests from /usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3 .. Error in test checkReconnectSwitch (ZEO.tests.testConnection.FileStorageReconnectionTests) Traceback (most recent call last): File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZEO/tests/ConnectionTests.py", line 122, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes ... [snip: many error messages] == ERROR: checkReadMethods (ZEO.tests.testZEO.MappingStorageTests) -- Traceback (most recent call last): File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZEO/tests/testZEO.py", line 136, in tearDown os.waitpid(pid, 0) OSError: [Errno 10] No child processes [snip: error messages] == FAIL: testUmask (zdaemon.tests.testzdrun.ZDaemonTests) -- Traceback (most recent call last): File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", line 244, in testUmask self.assert_(not os.access(path, os.W_OK)) File "/usr/lib/python2.3/unittest.py", line 278, in failUnless if not expr: raise self.failureException, msg AssertionError == ERROR: check7ZODBThreads (ZODB.tests.testMappingStorage.MappingStorageTests) -- Traceback (most recent call last): File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/tests/MTStorage.py", line 216, in check7ZODBThreads self._checkNThreads(7, ZODBClientThread, db, self) File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/tests/MTStorage.py", line 205, in _checkNThreads t.join(60) File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/tests/MTStorage.py", line 39, in run self.runtest() File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/tests/MTStorage.py", line 69, in runtest self.commit(d, i) File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/tests/MTStorage.py", line 75, in commit transaction.commit() File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/transaction/__init__.py", line 31, in commit manager.get().commit(sub) File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/transaction/_transaction.py", line 314, in commit s.afterCompletion(self) File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/Connection.py", line 747, in afterCompletion self._flush_invalidations() File "/usr2/local/buildirs/zope_plone/ZopeX3-3.0.0/build/lib.linux-i686-2.3/ZODB/Connection.py", line 750, in _flush_invalidations self._inv_lock.acquire() AttributeError: 'Connection' object has no attribute '_inv_lock' -- Ran 3970 tests in 383.228s FAILED (fai
