Re: [Zope3-Users] make check [OSX v3.3.0]

2006-10-10 Thread Jim Fulton

Robert Hicks wrote:

I get the following error and it is the only one:

Error in test checkVerificationInvalidationPersists 
(ZEO.tests.testConnection.MappingStorageConnectionTests)

Traceback (most recent call last):
  File 
/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/unittest.py, 
line 260, in run

testMethod()
  File 
/usr/local/src/Zope-3.3.0/build/lib.macosx-10.4-fat-2.4/ZEO/tests/ConnectionTests.py, 
line 534, in checkVerificationInvalidationPersists

self._storage = self.openClientStorage('test')
  File 
/usr/local/src/Zope-3.3.0/build/lib.macosx-10.4-fat-2.4/ZEO/tests/ConnectionTests.py, 
line 186, in openClientStorage

realm=realm)
  File 
/usr/local/src/Zope-3.3.0/build/lib.macosx-10.4-fat-2.4/ZEO/ClientStorage.py, 
line 321, in __init__

self._wait(wait_timeout)
  File 
/usr/local/src/Zope-3.3.0/build/lib.macosx-10.4-fat-2.4/ZEO/ClientStorage.py, 
line 342, in _wait

assert self._connection.is_async()
AttributeError: 'NoneType' object has no attribute 'is_async'


Is that a big deal?


Probably not, butplease submit a collector issue at:

  http://www.zope.org/Collectors/Zope3-dev

Please include information about whether this was a PPC or intel mac
and the OS version.

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] make check

2005-10-27 Thread Jim Fulton

Sorry, where are you looking at this.

In the release, the permissions are correct.

In an installation created with Python 2.4, the bits are not.

What version of Python are you using?

Jim

Paul Dumais wrote:

Sent this using the wrong  account:

On 10/26/05, Paul Dumais [EMAIL PROTECTED] wrote:


Hi Jim,

The execute bit seems OK:

-rwxr-xr-x  1 root root59 2005-10-02 12:48 donothing.sh

I get more errors if I run as root (the above one included). Ubuntu
does something tricky to the root account so that you cannot su root.
You have to sudo 'command' to do root tasks. I suspect this difference
is why I get more errors when I do sudo make check.

Since I am running make check as a user on the system, I though I
would try chown 'user' donothing.sh. Doing this gives the same error
when I run 'make check'.

I guess this begs the question: should I be looking to chown 'user' a
bunch of files and directories (since I plan to run everything as a
user)? Should I be looking to get rid of the su  root lockout feature
of Ubuntu? Hopefully none of this should be necessary since my 'user'
is a superuser.

I guess this is not a major problem, since Steve is safely ignoring
the error. Thanks for the quick replies! I read some posts from August
that mentioned that it may just be an issue of a slower machine (my
machine has a few other processes running on it). Increasing the error
threshold to something higher may be what's needed?

Paul


On 10/26/05, Jim Fulton [EMAIL PROTECTED] wrote:


Jim Fulton wrote:


Stephan Richter wrote:



On Wednesday 26 October 2005 16:26, Jim Fulton wrote:



AssertionError: spawned process failed to start in a minute

Is this serious? How could I get this test to pass?



Don't run the tests as root.




I see this error sporatically using a non-root user as well. I just
never worry about it. :-)



Right.  This is not what I thought it was.

This is something that I diagnosed and thought I fixed
a few weeks ago.

I'll look at it.


OK, Tim helped me remember what was going on with this.

I predict you can make this test pass by setting the execute bit on
the script donothing.sh in zdaemon/tests in the installation.
This test is trying to execute this script and can't because the
execute bits got cleared in the release process.

The test really should be rewritten to write the shell script itself
and set the permissions to whatever it wants.

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org




___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users



--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[Zope3-Users] make check

2005-10-26 Thread Paul Dumais
Hi all,

I have one error:

Ran 6991 tests in 333.025s

FAILED (failures=1)

when doing make check on a Zope-3.1.0 build on Ubuntu Linux. In short it is:

Failure in test testRunIgnoresParentSignals (zdaemon.tests.testzdrun.ZDaemonTest
s)
Traceback (most recent call last):
  File /usr/lib/python2.4/unittest.py, line 260, in run
testMethod()
  File /home/paul/Zope-3.1.0/build/lib.linux-i686-2.4/zdaemon/tests/testzdrun.p
y, line 237, in testRunIgnoresParentSignals
self.assert_(is_started, spawned process failed to start in a minute)
  File /usr/lib/python2.4/unittest.py, line 309, in failUnless
if not expr: raise self.failureException, msg
AssertionError: spawned process failed to start in a minute

Is this serious? How could I get this test to pass?

Thanks,

Paul
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] make check

2005-10-26 Thread Jim Fulton

Paul Dumais wrote:

Hi all,

I have one error:

Ran 6991 tests in 333.025s

FAILED (failures=1)

when doing make check on a Zope-3.1.0 build on Ubuntu Linux. In short it is:

Failure in test testRunIgnoresParentSignals (zdaemon.tests.testzdrun.ZDaemonTest
s)
Traceback (most recent call last):
  File /usr/lib/python2.4/unittest.py, line 260, in run
testMethod()
  File /home/paul/Zope-3.1.0/build/lib.linux-i686-2.4/zdaemon/tests/testzdrun.p
y, line 237, in testRunIgnoresParentSignals
self.assert_(is_started, spawned process failed to start in a minute)
  File /usr/lib/python2.4/unittest.py, line 309, in failUnless
if not expr: raise self.failureException, msg
AssertionError: spawned process failed to start in a minute

Is this serious? How could I get this test to pass?


Don't run the tests as root.

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] make check

2005-10-26 Thread Stephan Richter
On Wednesday 26 October 2005 16:26, Jim Fulton wrote:
  AssertionError: spawned process failed to start in a minute
 
  Is this serious? How could I get this test to pass?

 Don't run the tests as root.

I see this error sporatically using a non-root user as well. I just never 
worry about it. :-)

Regards,
Stephan
-- 
Stephan Richter
CBU Physics  Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] make check

2005-10-26 Thread Paul Dumais
Sent this using the wrong  account:

On 10/26/05, Paul Dumais [EMAIL PROTECTED] wrote:
 Hi Jim,

 The execute bit seems OK:

 -rwxr-xr-x  1 root root59 2005-10-02 12:48 donothing.sh

 I get more errors if I run as root (the above one included). Ubuntu
 does something tricky to the root account so that you cannot su root.
 You have to sudo 'command' to do root tasks. I suspect this difference
 is why I get more errors when I do sudo make check.

 Since I am running make check as a user on the system, I though I
 would try chown 'user' donothing.sh. Doing this gives the same error
 when I run 'make check'.

 I guess this begs the question: should I be looking to chown 'user' a
 bunch of files and directories (since I plan to run everything as a
 user)? Should I be looking to get rid of the su  root lockout feature
 of Ubuntu? Hopefully none of this should be necessary since my 'user'
 is a superuser.

 I guess this is not a major problem, since Steve is safely ignoring
 the error. Thanks for the quick replies! I read some posts from August
 that mentioned that it may just be an issue of a slower machine (my
 machine has a few other processes running on it). Increasing the error
 threshold to something higher may be what's needed?

 Paul


 On 10/26/05, Jim Fulton [EMAIL PROTECTED] wrote:
  Jim Fulton wrote:
   Stephan Richter wrote:
  
   On Wednesday 26 October 2005 16:26, Jim Fulton wrote:
  
   AssertionError: spawned process failed to start in a minute
  
   Is this serious? How could I get this test to pass?
  
  
   Don't run the tests as root.
  
  
  
   I see this error sporatically using a non-root user as well. I just
   never worry about it. :-)
  
  
   Right.  This is not what I thought it was.
  
   This is something that I diagnosed and thought I fixed
   a few weeks ago.
  
   I'll look at it.
 
  OK, Tim helped me remember what was going on with this.
 
  I predict you can make this test pass by setting the execute bit on
  the script donothing.sh in zdaemon/tests in the installation.
  This test is trying to execute this script and can't because the
  execute bits got cleared in the release process.
 
  The test really should be rewritten to write the shell script itself
  and set the permissions to whatever it wants.
 
  Jim
 
  --
  Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
  CTO  (540) 361-1714http://www.python.org
  Zope Corporation http://www.zope.com   http://www.zope.org
 

___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users