[TCLCORE] Timer.test failure on RHEL 3 clone (Tao Linux)

[C. R. O. <cr...@nc...>]

Greetings,

I'm getting an intermittent timer.test failure on RHEL 3 (actually Tao
Linux, a RHEL clone).

[cro@vmware-local unix]$ make test TESTFLAGS=3D"-file timer.test"
Warning: tclStubInit.c may be out of date.
Developers may want to run "make genstubs" to regenerate.
This warning can be safely ignored, do not report as a bug!
LD_LIBRARY_PATH=3D`pwd`:; export LD_LIBRARY_PATH; \
TCL_LIBRARY=3D"/usr/local/src/tcl8.4.5/library"; export TCL_LIBRARY; \
./tcltest ./../tests/all.tcl -file timer.test=20
Tests running in interp:  /usr/local/src/tcl8.4.5/unix/tcltest
Tests located in:  /usr/local/src/tcl8.4.5/tests
Tests running in:  /usr/local/src/tcl8.4.5/unix
Temporary files stored in /usr/local/src/tcl8.4.5/unix
Test files run in separate interpreters
Running tests that match:  *
Skipping test files that match:  l.*.test
Only running test files that match:  timer.test
Tests began at Wed Feb 25 06:54:20 AM MST 2004
timer.test

=3D=3D=3D=3D timer-1.1 Tcl_CreateTimerHandler procedure FAILED
=3D=3D=3D=3D Contents of test case:

    foreach i [after info] {
        after cancel $i
    }
    set x ""
    foreach i {100 200 1000 50 150} {
        after $i lappend x $i
    }
    after 200
    update
    set x

---- Result was:
50 100 150
---- Result should have been (exact matching):
50 100 150 200
=3D=3D=3D=3D timer-1.1 FAILED


=3D=3D=3D=3D timer-3.4 TimerHandlerEventProc procedure: all expired =
timers fire
FAILED
=3D=3D=3D=3D Contents of test case:

    foreach i [after info] {
        after cancel $i
    }
    set x {}
    after 100 lappend x a
    after 200 lappend x b
    after 300 lappend x c
    after 300
    vwait x
    set x

---- Result was:
a b
---- Result should have been (exact matching):
a b c
=3D=3D=3D=3D timer-3.4 FAILED


Tests ended at Wed Feb 25 06:54:26 AM MST 2004
all.tcl:        Total   51      Passed  49      Skipped 0       Failed
2
Sourced 1 Test Files.
Files with failing tests: timer.test

Sorry for my ignorance.  Do I open a bug report on this?  Or is there
something funny with RHEL?  I also have a RH9 install that did not
exhibit this behavior.  Do I even need to be concerned about this?


--=20
C. R. Oldham
Director of Technology
NCA CASI=20