Tcl Source Code

View Ticket
Login
2026-10-21
10:03 • Closed ticket [3605722fff]: chanio.test has 3 tests, that didn't run indepen... artifact: 9cdc6ea260 user: serhiy.storchaka
2013-02-26
20:43 • Closed ticket [3605120fff]: test chan-io-28.7 slightly buggy (doesn't run st... artifact: e9056ef98c user: dkf
2013-02-17
22:36 • New ticket [3605120fff]. artifact: 92b8b7b2fc user: pointsman

Ticket UUID: 3605120
Title: test chan-io-28.7 slightly buggy (doesn't run standalone)
Type: Bug Created on: 2013-02-17 22:36:27
Submitter: pointsman Assigned to: dkf
Subsystem: 24. Channel Commands Severity:
Priority: 5 Medium Last modified: 2013-02-26 20:43:16
Status: Closed Closed by: dkf
Resolution: Fixed Closed on: 2013-02-26 13:43:16
Version: current: 8.6.0
Description:
The test chan-io-28.7 out of tests/chanio doesn't run standalone. 

A call like

./tcltest ../tests/all.tcl -file chanio.test -match 'chan-io-28.7'

simply runs forever, the test doesn't terminate.

The reason is simple: The test, called as above, calls vwait on the variable name "" (the empty string), but this variable isn't set by the test. 

More Details: The test body calls

    vwait [namespace which -variable done]

Since there isn't a variable "done" neither defined nor created within the test, the [namespace which] call returns the empty string. In the typical case of running the whole test file this isn't noticed, because the test chan-io-28.6 does create (and define)  the variable done. Since all test bodies are evaluated in the same namespace (the global one) the [namespace which -variable done] call in chan-io-28.7 will return the right fqn, if chan-io-28.6 run before.

The fix is obvious: Either replace the 
    vwait [namespace which -variable done]
with a simple
    vwait done
or add a
    variable done
at the end of the -setup code of that test, as chan-io-28.6 does
User Comments:
dkf added on 2013-02-26 20:43:16:

allow_comments - 1

There was quite a bit of confusion in that test about which namespace the code was operating in. All tidied up.