This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: test_multiprocessing seems fragile
Type: Stage:
Components: Library (Lib), Tests Versions: Python 3.0
process
Status: closed Resolution: duplicate
Dependencies: Superseder:
Assigned To: jnoller Nosy List: jnoller, pitrou, roudkerk
Priority: normal Keywords:

Created on 2008-06-14 00:07 by pitrou, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg68194 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2008-06-14 00:07
I had the following intermittent failure under py3k:

[...]
test_multiprocessing
Process Process-24:
Traceback (most recent call last):
  File "/home/antoine/py3k/context/Lib/multiprocessing/process.py", line
237, in _bootstrap
    self.run()
  File "/home/antoine/py3k/context/Lib/multiprocessing/process.py", line
93, in run
    self._target(*self._args, **self._kwargs)
  File "/home/antoine/py3k/context/Lib/test/test_multiprocessing.py",
line 1390, in _remote
    client.connect(address)
socket.error: [Errno 111] Connection refused
msg68219 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2008-06-14 21:12
Apparently the error can happen in test_pickling:

test_pickling (__main__.WithProcessesTestPicklingConnections) ...
Process Process-24:
Traceback (most recent call last):
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
    self.run()
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 93, in run
    self._target(*self._args, **self._kwargs)
  File "Lib/test/test_multiprocessing.py", line 1390, in _remote
    client.connect(address)
socket.error: [Errno 111] Connection refused
msg68220 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2008-06-14 21:15
Oh, in another regrtest run, test_multiprocessing just hanged without
eating any CPU, this is what it printed after I pressed Ctrl-C:

test_multiprocessing
Process PoolWorker-5:4:
Traceback (most recent call last):
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:3:
Traceback (most recent call last):
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:2:
Traceback (most recent call last):
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:1:
Traceback (most recent call last):
  File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
msg68238 - (view) Author: Jesse Noller (jnoller) * (Python committer) Date: 2008-06-15 15:21
See: http://bugs.python.org/msg68237

For Beta 1 I am proposing a reduced test suite to remove the more 
unreliable tests.
msg68243 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2008-06-15 17:43
Le dimanche 15 juin 2008 à 15:21 +0000, Jesse Noller a écrit :
> 
> For Beta 1 I am proposing a reduced test suite to remove the more 
> unreliable tests.

This would be nice (especially the tests which make regrtest hang).
I also suggest the offending tests be commented out rather than
completely removed, so that we remember they were here :-)
msg71369 - (view) Author: Jesse Noller (jnoller) * (Python committer) Date: 2008-08-18 19:43
the "socket.error: [Errno 111] Connection refused" is fixed/resolved with 
the fix for issue 3270
History
Date User Action Args
2022-04-11 14:56:35adminsetgithub: 47359
2008-08-18 19:43:07jnollersetstatus: open -> closed
resolution: duplicate
messages: + msg71369
2008-06-15 17:43:35pitrousetmessages: + msg68243
2008-06-15 15:21:35jnollersetmessages: + msg68238
2008-06-14 21:15:29pitrousetmessages: + msg68220
2008-06-14 21:12:11pitrousetmessages: + msg68219
2008-06-14 19:26:45jnollersetassignee: jnoller
2008-06-14 19:26:29jnollersetnosy: + roudkerk
2008-06-14 01:39:56benjamin.petersonsetnosy: + jnoller
2008-06-14 00:07:53pitroucreate