mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 14:21:25 +02:00
c8dc20a825
Two regtest regularly fail in a random fashion depending on the machine's load (one could really wonder if it's really worth keeping such unreproducible tests) : - tcp-check_multiple_ports.vtc - 4be_1srv_smtpchk_httpchk_layer47errors.vtc It happens that one of the reason is the time it takes to connect to the local socket (hence the load-dependent aspect): if connect() on the loopback returns EINPROGRESS then this status is reported instead of a real error. Normally such a test is expected to see the error cleaned by tcp_connect_probe() but it really depends on the timing and instead we may very well send() first and see this error. The problem is that everything is collected based on errno, hoping it won't get molested in the way from the last unsuccesful syscall to wake_srv_chk(), which obviously is hard to guarantee. This patch at least makes sure that a few non-errors are reported as zero just like EAGAIN. It doesn't fix the root cause but makes it less likely to report incorrect failures. This fix could be backported as far as 1.9.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)