Mailing List Archive

Summary of messages to the zope-tests list.
Period Sun Jan 9 12:01:01 2005 UTC to Mon Jan 10 12:01:01 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (failures=2) : Zope-2_7-branch Python-2.3.4 :
Linux
From: Zope Unit Tests
Date: Mon Jan 10 00:00:44 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001393.html

Subject: FAILED (failures=2) : Zope-2_7-branch Python-2.4 :
Linux
From: Zope Unit Tests
Date: Mon Jan 10 00:03:14 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001394.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Sun Jan 9 23:55:44 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001391.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 9 23:58:14 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001392.html

Subject: OK : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 10 00:05:44 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001395.html

Subject: OK : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 10 00:08:14 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001396.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Wed Jan 12 12:01:02 2005 UTC to Thu Jan 13 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (failures=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:19:15 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001413.html

Subject: FAILED (failures=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:21:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001414.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:09:14 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001409.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:11:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001410.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:14:15 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001411.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 13 00:16:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001412.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Fri Jan 14 12:01:01 2005 UTC to Sat Jan 15 12:01:01 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (failures=1,
errors=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:19:15 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001425.html

Subject: FAILED (failures=1,
errors=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:21:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001426.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:09:15 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001421.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:11:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001422.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:14:15 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001423.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 15 00:16:45 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001424.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Zope tests summarizer wrote:
> Summary of messages to the zope-tests list.
> Period Fri Jan 14 12:01:01 2005 UTC to Sat Jan 15 12:01:01 2005 UTC.
> There were 6 messages: 6 from Zope Unit Tests.
>
>
> Test failures
> -------------
>
> Subject: FAILED (failures=1,
> errors=1) : Zope-trunk Python-2.3.4 : Linux
> From: Zope Unit Tests
> Date: Sat Jan 15 00:19:15 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001425.html
>
> Subject: FAILED (failures=1,
> errors=1) : Zope-trunk Python-2.4 : Linux
> From: Zope Unit Tests
> Date: Sat Jan 15 00:21:45 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001426.html

The 'testRoman' failures are do to the current state of docutils on the
HEAD in subversion; I think Jim and Andreas are scheduled to 'svn cp'
over the docutils used by Zope3 next week.

The other failure, in 'testRunIgnoresParentSignals', is the one which
Tim despairs of ever fixing :(

Tres.
--
===============================================================
Tres Seaver tseaver@zope.com
Zope Corporation "Zope Dealers" http://www.zope.com

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

--On Samstag, 15. Januar 2005 10:17 Uhr -0500 Tres Seaver
<tseaver@zope.com> wrote:

> Zope tests summarizer wrote:
>> Summary of messages to the zope-tests list.
>> Period Fri Jan 14 12:01:01 2005 UTC to Sat Jan 15 12:01:01 2005 UTC.
>> There were 6 messages: 6 from Zope Unit Tests.
>>
>>
>> Test failures
>> -------------
>>
>> Subject: FAILED (failures=1,
>> errors=1) : Zope-trunk Python-2.3.4 : Linux
>> From: Zope Unit Tests
>> Date: Sat Jan 15 00:19:15 EST 2005
>> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001425.html
>>
>> Subject: FAILED (failures=1,
>> errors=1) : Zope-trunk Python-2.4 : Linux
>> From: Zope Unit Tests
>> Date: Sat Jan 15 00:21:45 EST 2005
>> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001426.html
>
> The 'testRoman' failures are do to the current state of docutils on the
> HEAD in subversion; I think Jim and Andreas are scheduled to 'svn cp'
> over the docutils used by Zope3 next week.
>
> The other failure, in 'testRunIgnoresParentSignals', is the one which Tim
> despairs of ever fixing :(
>

The trunk should be working again.

-aj




_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Andreas Jung wrote:
>
>
> --On Samstag, 15. Januar 2005 10:17 Uhr -0500 Tres Seaver
> <tseaver@zope.com> wrote:
>
>> Zope tests summarizer wrote:
>>
>>> Summary of messages to the zope-tests list.
>>> Period Fri Jan 14 12:01:01 2005 UTC to Sat Jan 15 12:01:01 2005 UTC.
>>> There were 6 messages: 6 from Zope Unit Tests.
>>>
>>>
>>> Test failures
>>> -------------
>>>
>>> Subject: FAILED (failures=1,
>>> errors=1) : Zope-trunk Python-2.3.4 : Linux
>>> From: Zope Unit Tests
>>> Date: Sat Jan 15 00:19:15 EST 2005
>>> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001425.html
>>>
>>> Subject: FAILED (failures=1,
>>> errors=1) : Zope-trunk Python-2.4 : Linux
>>> From: Zope Unit Tests
>>> Date: Sat Jan 15 00:21:45 EST 2005
>>> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001426.html
>>
>>
>> The 'testRoman' failures are do to the current state of docutils on the
>> HEAD in subversion; I think Jim and Andreas are scheduled to 'svn cp'
>> over the docutils used by Zope3 next week.
>
>
> I am trying to fix this tomorrow. Zope 2.7.4 had a higher prio for me.

Right. I wasn't complaining, just trying to let zope-coders know that
those tests would be broken until you did have time to complete that
migration.

Tres.
--
===============================================================
Tres Seaver tseaver@zope.com
Zope Corporation "Zope Dealers" http://www.zope.com

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[Tres Seaver]
...
> The other failure, in 'testRunIgnoresParentSignals', is the one which
> Tim despairs of ever fixing :(

And there are two reasons for that. First, it's part of the zdaemon
tests, and nobody feels they "own" zdaemon, so nobody ever looks at
it. Second, Tim normally runs on Windows, where zdaemon is a big fat
no-op (Windows doesn't have Unixish signals, so the zdaemon tests are
skipped on Windows); whenever I've tried this test on a Linux box, it
passed.

According to all the signal esoterica I recall from my Unix days,
testRunIgnoresParentSignals _should_ pass on every platform that
supports Unixy signals. So on boxes where it fails, it's never going
to get fixed unless & until people on such boxes do some work to
figure out _why_ it's failing. It can't be that hard (it's a very
short & simple test), it seems more that just nobody can be convinced
to bother trying.

I can just note that like many tests involving multiple processes,
it's vulnerable to platform timing accidents. As a comment in the
test says,

time.sleep(2) # race condition possible here

If you're running the test on a box so feeble or overburdened that it
takes more than 2 seconds for the line before that to get a new
spawned process running, the test will fail. For someone on a box
where this test does fail, that's the first thing to determine: is
the test failing because spawnvp is pig-slow on that box, or for some
other reason (and if so, what?)?
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Sat Jan 15 12:01:01 2005 UTC to Sun Jan 16 12:01:01 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (failures=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:16:35 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001431.html

Subject: FAILED (failures=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:19:05 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001432.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:06:34 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001427.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:09:04 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001428.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:11:34 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001429.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Sun Jan 16 00:14:04 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001430.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Right. The test only fails in the nightly runs. It passes fine when I
run the tests from the command line. Let's see what I can do about
that...

Stefan


On 16. Jän 2005, at 00:51, Tim Peters wrote:

> I can just note that like many tests involving multiple processes,
> it's vulnerable to platform timing accidents. As a comment in the
> test says,
>
> time.sleep(2) # race condition possible here
>
> If you're running the test on a box so feeble or overburdened that it
> takes more than 2 seconds for the line before that to get a new
> spawned process running, the test will fail. For someone on a box
> where this test does fail, that's the first thing to determine: is
> the test failing because spawnvp is pig-slow on that box, or for some
> other reason (and if so, what?)?
>
--
The time has come to start talking about whether the emperor is as well
dressed as we are supposed to think he is. /Pete McBreen/

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[Stefan H. Holek, on testRunIgnoresParentSignals]
> Right. The test only fails in the nightly runs. It passes fine when I
> run the tests from the command line. Let's see what I can do
> about that...

A good start would be to rewrite the test, so that it becomes possible
to guess something about the cause of failure when it does fail. For
example, the test's

try:
response = send_action('status\n', zdrun_socket) or ''
except socket.error, msg:
response = ''

is silly, because send_action() suppresses socket.error. IOW, the
try/except block here is useless. Better would be, e.g.,

response = (send_action('status\n', zdrun_socket) or
"send_action failed")

Better still may be to change send_action() to record why it fails
when it fails.

Then the actual raising of a failure loses all useful information:

self.assert_(len(params) > 1)

That doesn't tell you whether the response was empty, or not empty but
not of the expected form, or what. Better here would be, e.g.,

if '\n' not in response:
self.fail("expected at least one newline in response %r" %
response)

*If* it's failing because spawnvp doesn't have time to get the new
processes running, what actually happens in this test is that its
first send_action() call suppresses a socket.error with a detail of
the form

(2, 'No such file or directory')

The test turns send_action's None return in that case into an empty
string, and then splitting an empty string by '\n' yields the list

['']

and so

self.assert_(len(params) > 1)

triggers. I'm guessing that is what's happening, too, but it's
impossible to be sure of that now from the test's useless failure
output.
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Sun Jan 16 12:01:01 2005 UTC to Mon Jan 17 12:01:01 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (failures=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:17:52 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001437.html

Subject: FAILED (failures=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:20:22 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001438.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:07:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001433.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:10:21 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001434.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:12:52 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001435.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Mon Jan 17 00:15:22 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001436.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Mon Jan 17 12:01:02 2005 UTC to Tue Jan 18 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (errors=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:18:02 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001443.html

Subject: FAILED (errors=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:20:32 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001444.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:08:01 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001439.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:10:31 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001440.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:13:01 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001441.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Tue Jan 18 00:15:31 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001442.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[Tim Peters, on testRunIgnoresParentSignals]
...
> *If* it's failing because spawnvp doesn't have time to get the new
> processes running, what actually happens in this test is that its
> first send_action() call suppresses a socket.error with a detail of
> the form
>
> (2, 'No such file or directory')
>
> The test turns send_action's None return in that case into an
> empty string, and then splitting an empty string by '\n' yields
> the list
>
> ['']
>
> and so
>
> self.assert_(len(params) > 1)
>
> triggers. I'm guessing that is what's happening, too, but it's
> impossible to be sure of that now from the test's useless failure
> output.

And after you changed send_action() to stop suppressing socket.error,
the overnight test run failed like so:

ERROR: testRunIgnoresParentSignals (zdaemon.tests.testzdrun.ZDaemonTests)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/local/python2.4/lib/python2.4/unittest.py", line 260, in run
testMethod()
File "/autotest/temp/python24-zope28/lib/python/zdaemon/tests/testzdrun.py",
line 223, in testRunIgnoresParentSignals
response = send_action('status\n', zdrun_socket) or ''
File "/autotest/temp/python24-zope28/lib/python/zdaemon/tests/testzdrun.py",
line 257, in send_action
sock.connect(sockname)
File "<string>", line 1, in connect
error: (2, 'No such file or directory')

Good (I guess <wink>). The next question is why 2 seconds isn't long
enough to get the spawned processes running on this box.

Or maybe just boosting the sleep(2) in the test to, say, sleep(10),
would make the problem go away? I don't care if the tests always take
8 seconds longer to run, if in return people can stop wasting time
wondering why this test sometimes fails.

A more principled approach would retry the connect() until it worked,
or until (say) a minute had passed. On all boxes I've tried, sleep(1)
is long enough for the test to pass reliably. Maybe you have a cron
job that sucks up a lot resources while your overnight tests are
running?
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Tue Jan 18 12:01:02 2005 UTC to Wed Jan 19 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (errors=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:14:11 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001449.html

Subject: FAILED (errors=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:16:41 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001450.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:04:10 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001445.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:06:40 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001446.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:09:10 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001447.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 00:11:41 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001448.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

On 18. Jän 2005, at 19:46, Tim Peters wrote:

> Good (I guess <wink>). The next question is why 2 seconds isn't long
> enough to get the spawned processes running on this box.

The box is an ex desktop machine that got liberated to run *nix and act
as my mail server. Not exactly screaming.

> is long enough for the test to pass reliably. Maybe you have a cron
> job that sucks up a lot resources while your overnight tests are
> running?

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.

Stefan


--
The time has come to start talking about whether the emperor is as well
dressed as we are supposed to think he is. /Pete McBreen/

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[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).
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Wed Jan 19 12:01:02 2005 UTC to Thu Jan 20 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (errors=1) : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:25:55 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001455.html

Subject: FAILED (errors=1) : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:28:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001456.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:15:54 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001451.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:18:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001452.html

Subject: OK : Zope-2_7-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:20:55 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001453.html

Subject: OK : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Wed Jan 19 23:23:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001454.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[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.

And is that what you did? I noticed that your overnight tests have
passed two nights in a row now. I don't know what you did, so the
mystery is still open.
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

I have increased the sleep timeout to 30 seconds (locally). Lowering
the value now to find out when it starts to bork.

Stefan


On 21. Jän 2005, at 16:09, Tim Peters wrote:

> [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.
>
> And is that what you did? I noticed that your overnight tests have
> passed two nights in a row now. I don't know what you did, so the
> mystery is still open.
--
The time has come to start talking about whether the emperor is as well
dressed as we are supposed to think he is. /Pete McBreen/

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

[Stefan H. Holek]
> I have increased the sleep timeout to 30 seconds (locally).
> Lowering the value now to find out when it starts to bork.

Note that I just checked in a different approach. The test now
queries send_action() in a loop, for up to a minute, until
send_action() says the child is running. On most boxes the test
should run faster now. I expect it will repair the failures on your
box, but won't know for sure until I know you've tried it.
_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Fri Jan 21 12:01:02 2005 UTC to Sat Jan 22 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.3.4 :
Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:18:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001465.html

Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:20:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001466.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:14:24 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001463.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:16:24 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001464.html

Subject: OK : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:22:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001467.html

Subject: OK : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Fri Jan 21 23:24:25 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001468.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Summary of messages to the zope-tests list.
Period Sat Jan 22 12:01:02 2005 UTC to Sun Jan 23 12:01:02 2005 UTC.
There were 6 messages: 6 from Zope Unit Tests.


Test failures
-------------

Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.3.4 :
Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:10:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001471.html

Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:12:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001472.html


Tests passed OK
---------------

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:06:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001469.html

Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:08:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001470.html

Subject: OK : Zope-trunk Python-2.3.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:14:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001473.html

Subject: OK : Zope-trunk Python-2.4 : Linux
From: Zope Unit Tests
Date: Sat Jan 22 23:16:51 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001474.html

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

Stefan,

I think the failing tests are caused by your changes to testAcquisition.py
(or it has been added).
Please fix!

Andreas


Zope Unit Tests : FAILED (errors=6)
Zope-2_7-branch Python-2.3.4 : Linux

Running /usr/local/python2.3/bin/python test.py
Script (Python):filepath:1: DeprecationWarning: integer argument expected,
got float
======================================================================
ERROR: testAclUsersDenied (AccessControl.tests.testAcquisition.TestGetAttr)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 124, in testAclUsersDenied
o = guarded_getattr(self.folder.denied, 'acl_users')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'acl_users' in this context

======================================================================
ERROR: testErrorLogDenied (AccessControl.tests.testAcquisition.TestGetAttr)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 154, in testErrorLogDenied
o = guarded_getattr(self.folder.denied, 'error_log')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'error_log' in this context

======================================================================
ERROR: testAclUsersDenied
(AccessControl.tests.testAcquisition.TestGetAttrAnonymous)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 124, in testAclUsersDenied
o = guarded_getattr(self.folder.denied, 'acl_users')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'acl_users' in this context

======================================================================
ERROR: testAclUsersProtected
(AccessControl.tests.testAcquisition.TestGetAttrAnonymous)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 129, in testAclUsersProtected
o = guarded_getattr(self.folder.protected, 'acl_users')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'acl_users' in this context

======================================================================
ERROR: testErrorLogDenied
(AccessControl.tests.testAcquisition.TestGetAttrAnonymous)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 154, in testErrorLogDenied
o = guarded_getattr(self.folder.denied, 'error_log')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'error_log' in this context

======================================================================
ERROR: testErrorLogProtected
(AccessControl.tests.testAcquisition.TestGetAttrAnonymous)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/tests/testAcquisition.py",
line 159, in testErrorLogProtected
o = guarded_getattr(self.folder.protected, 'error_log')
File
"/autotest/temp/python23-zope27/lib/python/AccessControl/ImplPython.py",
line 554, in guarded_getattr
if validate(inst, inst, name, v):
Unauthorized: You are not allowed to access 'error_log' in this context

--On Samstag, 22. Januar 2005 12:01 Uhr +0000 Zope tests summarizer
<zopetests@z3u.com> wrote:

> Summary of messages to the zope-tests list.
> Period Fri Jan 21 12:01:02 2005 UTC to Sat Jan 22 12:01:02 2005 UTC.
> There were 6 messages: 6 from Zope Unit Tests.
>
>
> Test failures
> -------------
>
> Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.3.4 :
> Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:18:25 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001465.html
>
> Subject: FAILED (errors=6) : Zope-2_7-branch Python-2.4 : Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:20:25 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001466.html
>
>
> Tests passed OK
> ---------------
>
> Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:14:24 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001463.html
>
> Subject: OK : Zope-2_6-branch Python-2.3.4 : Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:16:24 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001464.html
>
> Subject: OK : Zope-trunk Python-2.3.4 : Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:22:25 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001467.html
>
> Subject: OK : Zope-trunk Python-2.4 : Linux
> From: Zope Unit Tests
> Date: Fri Jan 21 23:24:25 EST 2005
> URL: http://mail.zope.org/pipermail/zope-tests/2005-January/001468.html
>
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://mail.zope.org/mailman/listinfo/zope-coders




_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders

I checked in broken tests on purpose <sheepish grin>. I'd like to
discuss why they fail in Zope >= 2.7.3 and what to do about it ->
zope-dev.

Stefan

On 23. Jän 2005, at 14:00, Andreas Jung wrote:

> I think the failing tests are caused by your changes to
> testAcquisition.py (or it has been added).
> Please fix!
>
> Andreas
--
The time has come to start talking about whether the emperor is as well
dressed as we are supposed to think he is. /Pete McBreen/

_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://mail.zope.org/mailman/listinfo/zope-coders