Re: Re: Zope tests: 4 OK, 2 Failed

[Stefan H. Holek]
> Casual perusal of crontabs didn't point out anything. Bummer.
> Interestingly, the very same test on 2.7 branch appears to pass
> fine every night. I'll shift the jobs around a bit.

Another possibility, which only you can answer for your setup:  since
testRunIgnoresParentSignals uses a Unix domain socket, it's possible
that the permissions under which you run the overnight Zope tests are
such that the spawned processes can't create the Unix domain socket in
the zdaemon tests/ directory.  The test runner is in a different
process, and has no way to know it if that happens.  That's another
way the test runner could end up with a

   (2, 'No such file or directory')

socket.error when attempting to connect() to the (a non-existent) Unix
domain socket (which socket needs to be created by the spawned
processes -- and they'll fail to do that if the test runner's sleep()
isn't long enough for them to get started, _or_ if they don't have
sufficient permission to create the silly thing; there's no way to
distinguish these cases from the error output so far).