Tcl Source Code

OriginalBugID: 5834 RFE
Version: 8.3.1
SubmitDate: '2000-06-06'
LastModified: '2000-06-06'
Severity: LOW
Status: Assigned
Submitter: hobbs
ChangedBy: hobbs
OS: All
FixedDate: '2000-10-25'
ClosedDate: '2000-10-25'


The socket ports should be changed to use a different range of
values (less likely to conflict with other ports), and all use
of port numbers should be parametrized at the top of the tests.

Logged In: YES 
user_id=75003

Committed to head.

File Added - 10634: 219253.diff.3

Logged In: YES 
user_id=75003

Better patch which eliminates all fixed ports but the ones 
for 'doTestsWithRemoteServer'-tests. With this I consider 
the item as fixed.

File Added - 10619: 219253.diff

Logged In: YES 
user_id=75003

Adding a patch which fixes the problem at least partially.

Some tests (constraint 'doTestsWithRemoteServer') are 
unchanged. They are skipped when running the testsuite 
normally and seem to be designed for a more controlled 
environment. It is assumed that the free ports in this 
environment are known.

Also unchanged right now are 12.1, 12.2, 12.3 and 13.1. 
More thought is needed how to make the port number known to 
both server and client.

Logged In: YES 
user_id=79902

It is better to make it so that none of the tests require a
particular port number (you can *never* be sure that any
specific port will be available.)  Instead, create the
server socket on port 0 (i.e. get the OS to assign you an
unused port number) and use [fconfigure] to read off what
port you actually got.  Some tests do this already...