summaryrefslogtreecommitdiffstats
path: root/tests/socket.test
Commit message (Collapse)AuthorAgeFilesLines
* test for bug [c6ed4acfd8]: running async socket connect with other connect ↵oehhar2014-12-071-0/+18
| | | | established will block tcl as it goes in an infinite loop in vwait
* update changes; more test suite polishing.dgp2014-11-071-1/+1
|
* New tests: 14.16: -peername empty while async connect running, 14.17: -socknameoehhar2014-10-171-0/+22
|
* makeFile / removeFile balancedgp2014-07-101-0/+8
|
* [f652ae79ed] Close sockets used in tests, so as not to corrupt otherdgp2014-07-101-0/+1
| | | tests in the suite.
* merge socket test from 8.5dgp2014-06-161-0/+42
|\
| * Draft test for [1758a0b603].dgp2014-06-131-0/+41
| |
* | Tests socket*-2.12 test for DiscardOutput() updates.dgp2014-06-051-1/+39
|\ \ | |/
| * Test socket-2.12 covers the DiscardOutput() update.dgp2014-06-051-1/+39
| |
| * Moved tests socket-8.2 and socket-8.3 to socket-14.3 and socket-14.4 and ↵oehhar2014-04-041-29/+31
| |\ | | | | | | | | | made them robust against connect failures
| * \ Fix bug [581937ab1e]: fire readable event on async socket connect failurebug_581937ab1eoehhar2014-04-021-0/+17
| |\ \
| * | | Test to demonstrate bug [336441ed59]. Depends on timing and will not always ↵oehhar2014-04-021-0/+16
| | | | | | | | | | | | | | | | fire but is better than nothing. Reliable for me.
* | | | These edits make the tests socket-14.11.[01] stop hanging, but also introducedgp2014-06-021-1/+1
| | | | | | | | | | | | a whole raft of test failures. WIP.
* | | | Improve robustness of the socket tests against systems that support IPv6, ↵max2014-06-021-60/+75
| | | | | | | | | | | | | | | | but don't resolve localhost to ::1 (and vice versa for IPv4 and 127.0.0.1).
* | | | Fix c&p errors in test descriptionsmax2014-05-211-4/+4
| | | |
* | | | * Give clearer names to some of the state flags and sync them with ↵bug_13d3af3ad5max2014-04-081-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Windows where it makes sense. * Rework WaitForConnect once more to always report ENOTCONN on I/O operations on failed async sockets. * Fix synchronous connections to a server that only listens on IPv6 (or whatever comes later in the list returned by getaddrinfo(), socket-15.*) * Fix spurious writable event on async sockets (socket-14.15).
* | | | Changed error report logic, that an async connect error is only reported by ↵oehhar2014-04-081-6/+6
| |_|/ |/| | | | | | | | 'fconfigure -error' and not by a possible last command terminating the async connect. The terminating command always returns "socket is not connected" on connect error. In addition, some flags were renamed: TCP_ASYNC_SOCKET to TCP_NONBLOCKING and also the new state flags.
* | | Move tests 8.2 and 8.3 out of the IPv4/IPv6 loop to 14.13 and 14.14.max2014-04-041-31/+32
| | |
* | | Fix/improve tests.max2014-04-041-37/+30
| | |
* | | Add tests for bugs [336441ed59] and [581937ab1e] from core-8-5-branch.max2014-04-041-0/+29
| | |
* | | * Rework WaitForConnect() to fix synchronous completion of asynchronous ↵max2014-04-041-5/+8
| |/ |/| | | | | | | | | connections. * Let TcpInputProc() and TcpOutputProc() fail before calling any I/O syscalls when an asynchronous connection has failed. * Adjust the tests accordingly.
* | * More test improvements for async sockets.max2014-03-141-19/+26
| | | | | | | | * Advance async connections whenever the channel is touched (e.g. by [chan configure]). * Add a noblock argument to WaitForConnect(), so that advancing async connections from [chan configure] doesn't block even on a blocking socket.
* | * Hide transient errors of the internal iterations of [socket -async] ↵max2014-03-111-5/+155
| | | | | | | | | | from the script level. * More tests for corner cases.
* | WaitForConnect may only call back to CreateClientSocket when the socket is ↵max2014-03-101-2/+2
| | | | | | | | writable or something. When it does so for a pending socket, it is falsely assumed to have succeeded and a subsequent read/write operation will fail.
* | * tclUnixSock.c: Fix WaitForConnect() for client sockets that have to try ↵max2014-03-101-20/+179
| | | | | | | | | | | | more than one address. * socket.test: Extend and improve tests for [socket -async] * socket.test: Add latency measuring and calculation for Windows.
* | More debug to chase different fd in struct than in callbackoehhar2014-03-061-0/+6
| |
* | socket-14.6 only makes sense where both, IPv4 and IPv6 are supported.max2013-11-121-1/+1
| |
* | Fix [5425f2c082]: [fconfigure -error] breaks the background processing of a ↵max2013-11-121-0/+28
| | | | | | | | pending [socket -async].
* | Let all test-cases which require Thread, at least require Thread 2.7jan.nijtmans2012-11-161-1/+1
| |
* | Prevented intermittent test failure due to race condition.dkf2012-05-311-0/+1
| |
* | Update requirements to avoid old buggy Thread releases.dgp2012-05-211-1/+1
| |
* | 3428754 Test socket-14.2 tolerate [socket -async] connection that connectsdgp2012-05-031-9/+12
| | | | | | synchronously.
* | Made test socket-14.1 more robust to stop failure on OS X (Snow Leopard)dgp2011-09-161-0/+1
| |
* | 3390699 Convert [testthread] use to Thread package use in socket_*-13.1.dgp2011-09-111-19/+10
| | | | | | Eliminates a memory leak in `make valgrind`.
* | Rework constraint detection and add constraints that cater for the fact, ↵max2011-06-281-9/+22
| | | | | | | | that both address families might be available, but localhost only resolves to one of the loopback addreses.
* | replace socket-14.3 with a test that is more useful and less likely to ↵max2011-06-281-12/+17
| | | | | | | | randomly fail depending on the local network environment.
* | * unix/tclUnixSock.c (CreateClientSocket): Fix and simplify posting of ↵max2011-06-281-7/+60
| | | | | | | | | | the writable fileevent at the end of an asynchronous connection attempt. Improve comments for some of the trickery around [socket -async]. [Bug 3325339] * tests/socket.test: Adjust tests to the async code changes. Add more tests for corner cases of async sockets.
* | Merge fixes for [socket -async] and other improvements to the unix socket codemax2011-06-221-1/+85
|\ \
| * | complete a comment in socket.testrmax_ipv6_branchmax2011-06-221-1/+2
| | |
| * | * doc/socket.n: Document the fact that the event loop is now needed for ↵max2011-06-161-0/+3
| | | | | | | | | | | | | | | | | | [socket -async] * unix/tclUnixSock.c: Set up the file handler for async sockets to fire on exceptions in addition to writable state. * tests/socket.test: Improve error reporting when socket-14.2 times out.
| * | * Don't use port 0 for test 14.2 as it fails in different ways on Linux ↵max2011-06-061-2/+2
| | | | | | | | | | | | | | | | | | | | | and NetBSD. * Unify channel name creation. * Prevent error messages from appearing twice. * Double the measured latency in socket.test to be on the safe side.
| * | * Improve socket.test by checking the latency on the loopback address and ↵max2011-06-011-7/+30
| | | | | | | | | | | | | | | use that for some of the tests instead of fixed "big enough" times. * Improve correctness of [socket -async] in some error cases.
| * | * Fix setting up of [fileevent] while an async socket is still in progress max2011-05-301-2/+37
| | | | | | | | | | | | * Cache async socket errors for later use by [fconfigure -error] * Add tests for the above
| * | Fix [socket -async] for DNS names with more than one addressmax2011-05-271-0/+22
| | |
* | | Add test constraint, so 6.2 and 6.3 don't fail when the machine does not ↵jan.nijtmans2011-06-061-2/+2
|/ / | | | | | | | | have support for ip6 Follow-up to checkin from 2011-05-11 by rmax
* | fix a timing issue in socket-12.3max2011-05-271-1/+2
| |
* | * unix/tclUnixSock.c (TcpWatchProc): No need to check for server sockets ↵max2011-05-111-0/+18
| | | | | | | | | | here, as the generic server code already takes care of that. * tests/socket.test (accept): Add tests to make sure that this remains so.
* | Now that we're no longer using SCM based on RCS, the RCS Keyword linesdgp2011-03-021-2/+0
|\ \ | |/ | | cause more harm than good. Purged them (except in zlib files).
| * Now that we're no longer using SCM based on RCS, the RCS Keyword lines causedgp2011-03-021-2/+0
| |\ | | | | | | more harm than good. Purged them.
| | * Now that we're no longer using SCM based on RCS, the RCS Keyword lines causedgp2011-03-011-2/+0
| | | | | | | | | more harm than good. Purged them.