[Python-checkins] python/dist/src/Lib/test/output test_logging,1.3,1.4

[gvanrossum@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Lib/test/output
In directory sc8-pr-cvs1:/tmp/cvs-serv2824/output

Modified Files:
	test_logging 
Log Message:
New version from Vinaj, should solve the threading problems (hopefully).


Index: test_logging
===================================================================
RCS file: /cvsroot/python/python/dist/src/Lib/test/output/test_logging,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** test_logging	18 Feb 2003 14:20:04 -0000	1.3
--- test_logging	25 Apr 2003 14:22:00 -0000	1.4
***************
*** 26,30 ****
  CRITICAL:INF.BADPARENT.UNDEF:Message 23
  CRITICAL:INF.BADPARENT:Message 24
! INFO:INF:Messages should bear numbers 0 through 24.
  -- log_test0  end    ---------------------------------------------------
  -- log_test1  begin  ---------------------------------------------------
--- 26,30 ----
  CRITICAL:INF.BADPARENT.UNDEF:Message 23
  CRITICAL:INF.BADPARENT:Message 24
! INFO:INF:Finish up, it's closing time. Messages should bear numbers 0 through 24.
  -- log_test0  end    ---------------------------------------------------
  -- log_test1  begin  ---------------------------------------------------
***************
*** 512,515 ****
  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)
  -- logrecv output end    ---------------------------------------------------
--- 512,515 ----
  INF.BADPARENT.UNDEF -> CRITICAL: Message 23 (via logrecv.tcp.INF.BADPARENT.UNDEF)
  INF.BADPARENT -> CRITICAL: Message 24 (via logrecv.tcp.INF.BADPARENT)
! INF -> INFO: Finish up, it's closing time. Messages should bear numbers 0 through 24. (via logrecv.tcp.INF)
  -- logrecv output end    ---------------------------------------------------