➜
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.
Created on 2003-01-31 16:43 by jhylton, last changed 2022-04-10 16:06 by admin. This issue is now closed.
| Messages (7) | |||
|---|---|---|---|
| msg14320 - (view) | Author: Jeremy Hylton (jhylton)  |
Date: 2003-01-31 16:43 | |
When I run the test suite, test_logging sometimes
fails. It misses the following output and gets a bunch
of exceptions llike the one I included at the end. I
haven't counted, but I'd guess that there's one
traceback for each missing line of output.
test test_logging produced unexpected output:
**********************************************************************
*** lines 489-514 of expected output missing:
- ERR -> CRITICAL: Message 0 (via logrecv.tcp.ERR)
- ERR -> ERROR: Message 1 (via logrecv.tcp.ERR)
- INF -> CRITICAL: Message 2 (via logrecv.tcp.INF)
- INF -> ERROR: Message 3 (via logrecv.tcp.INF)
- INF -> WARN: Message 4 (via logrecv.tcp.INF)
- INF -> INFO: Message 5 (via logrecv.tcp.INF)
- INF.UNDEF -> CRITICAL: Message 6 (via
logrecv.tcp.INF.UNDEF)
- INF.UNDEF -> ERROR: Message 7 (via logrecv.tcp.INF.UNDEF)
- INF.UNDEF -> WARN: Message 8 (via logrecv.tcp.INF.UNDEF)
- INF.UNDEF -> INFO: Message 9 (via logrecv.tcp.INF.UNDEF)
- INF.ERR -> CRITICAL: Message 10 (via logrecv.tcp.INF.ERR)
- INF.ERR -> ERROR: Message 11 (via logrecv.tcp.INF.ERR)
- INF.ERR.UNDEF -> CRITICAL: Message 12 (via
logrecv.tcp.INF.ERR.UNDEF)
- INF.ERR.UNDEF -> ERROR: Message 13 (via
logrecv.tcp.INF.ERR.UNDEF)
- DEB -> CRITICAL: Message 14 (via logrecv.tcp.DEB)
- DEB -> ERROR: Message 15 (via logrecv.tcp.DEB)
- DEB -> WARN: Message 16 (via logrecv.tcp.DEB)
- DEB -> INFO: Message 17 (via logrecv.tcp.DEB)
- DEB -> DEBUG: Message 18 (via logrecv.tcp.DEB)
- UNDEF -> CRITICAL: Message 19 (via logrecv.tcp.UNDEF)
- UNDEF -> ERROR: Message 20 (via logrecv.tcp.UNDEF)
- UNDEF -> WARN: Message 21 (via logrecv.tcp.UNDEF)
- UNDEF -> INFO: Message 22 (via logrecv.tcp.UNDEF)
- INF.BADPARENT.UNDEF -> CRITICAL: Message 23 (via
logrecv.tcp.INF.BADPARENT.UNDEF)
- INF.BADPARENT -> CRITICAL: Message 24 (via
logrecv.tcp.INF.BADPARENT)
- INF -> INFO: Messages should bear numbers 0 through
24. (via logrecv.tcp.INF)
**********************************************************************
Traceback (most recent call last):
File
"/home/jeremy/src/python/dist/src/Lib/logging/__init__.py",
line 648, in emit
self.stream.write("%s\n" % msg)
ValueError: I/O operation on closed file
Traceback (most recent call last):
File
"/home/jeremy/src/python/dist/src/Lib/logging/__init__.py",
line 648, in emit
self.stream.write("%s\n" % msg)
ValueError: I/O operation on closed file
|
|||
| msg14321 - (view) | Author: Raymond Hettinger (rhettinger) *  |
Date: 2003-03-01 02:02 | |
Logged In: YES user_id=80475 Can this be closed? |
|||
| msg14322 - (view) | Author: Jack Jansen (jackjansen) * |
Date: 2003-03-03 10:40 | |
Logged In: YES user_id=45365 I see this problem on MacPython-OS9 too, occasionally. So if it is closed I would like to hear the resolution, please... |
|||
| msg14323 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2003-04-25 14:35 | |
Logged In: YES user_id=33168 This problem should be fixed, please test. |
|||
| msg14324 - (view) | Author: Jack Jansen (jackjansen) * |
Date: 2003-04-29 21:45 | |
Logged In: YES user_id=45365 On MacOS9 the problem is indeed fixed. |
|||
| msg14325 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2003-05-22 21:51 | |
Logged In: YES user_id=33168 Jeremy, do you still have this problem? I think all the test logging problems have been fixed now. |
|||
| msg14326 - (view) | Author: Jeremy Hylton (jhylton) |
Date: 2003-05-23 15:55 | |
Logged In: YES user_id=31392 I haven't seen the error in a while. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:06:21 | admin | set | github: 37878 |
| 2003-01-31 16:43:54 | jhylton | create | |