Created on 2010-04-18 22:27 by haypo, last changed 2011-04-12 22:58 by haypo. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg103542 - (view) | Author: STINNER Victor (haypo) *  |
Date: 2010-04-18 22:27 | |
http://www.python.org/dev/buildbot/builders/sparc Debian 3.1/builds/49/steps/test/logs/stdio test_subprocess * ob object : <refcnt 0 at 0x1038220> type : str refcount: 0 address : 0x1038220 * op->_ob_prev->_ob_next object : <refcnt 0 at 0x1038220> type : str refcount: 0 address : 0x1038220 * op->_ob_next->_ob_prev object : [29082 refs] . this bit of output is from a test of stdout in a different process ... . this bit of output is from a test of stdout in a different process ... test test_subprocess failed -- Traceback (most recent call last): File "/home/pybot/buildarea-sid/3.1.klose-debian-sparc/build/Lib/test/test_subprocess.py", line 459, in test_no_leaking data = p.communicate(b"lime")[0] File "/home/pybot/buildarea-sid/3.1.klose-debian-sparc/build/Lib/subprocess.py", line 727, in communicate return self._communicate(input) File "/home/pybot/buildarea-sid/3.1.klose-debian-sparc/build/Lib/subprocess.py", line 1203, in _communicate stdout, stderr = self._communicate_with_poll(input) File "/home/pybot/buildarea-sid/3.1.klose-debian-sparc/build/Lib/subprocess.py", line 1269, in _communicate_with_poll input_offset += os.write(fd, chunk) OSError: [Errno 32] Broken pipe |
|||
| msg103547 - (view) | Author: STINNER Victor (haypo) * |
Date: 2010-04-18 23:04 | |
"op->_ob_prev->_ob_next" comes from _Py_ForgetReference() compiled in pydebug mode and it should ends with "UNREF invalid object" but it looks like _PyObject_Dump(op->_ob_next->_ob_prev); crashed. Anyway, something gone wrong here. |
|||
| msg116104 - (view) | Author: Florent Xicluna (flox) * |
Date: 2010-09-11 16:00 | |
It still happens on the same builder, occasionally. http://www.python.org/dev/buildbot/builders/sparc%20Debian%203.1/builds/24 |
|||
| msg133611 - (view) | Author: STINNER Victor (haypo) * |
Date: 2011-04-12 22:58 | |
I did not see this failure since one year. flox saw it 7 months ago. I close this issue because I think that it is fixed. Reopen it if the issue was not fixed. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-04-12 22:58:35 | haypo | set | status: open -> closed resolution: out of date messages: + msg133611 |
| 2010-09-11 16:00:37 | flox | set | nosy:
+ flox messages: + msg116104 components: + Tests type: behavior |
| 2010-04-18 23:04:48 | haypo | set | messages: + msg103547 |
| 2010-04-18 22:27:57 | haypo | create | |