kc3-lang/libevent/test

Branch :


Log

Author Commit Date CI Message
2f656ffb 2019-01-20 22:40:57 test/buffer: write >GETPIPE_SZ via events over pair to avoid stall [ Upstream commit 0aad01436af27c5807d48701028020bb51cba387 ]
70a39d45 2018-10-31 00:09:38 Cover ET with multiple events for same fd [ Upstream commit 77c0e510581b88242d7d7bcff4954cedc5613554 ] Refs: #636
4d73149f 2014-03-18 12:35:39 Remove integer-overflow unit tests [ Upstream commit e5302ac7 ] [ Fixes clang builds -- https://travis-ci.org/azat/libevent/jobs/446053765 ] There's not much point checking undefined behavior.
33845824 2014-03-18 18:36:32 Correctly skip ipv6 http test on systems without ipv6 [ Upstream commit 6a1c4d50 ]
b52e95f5 2014-03-12 18:13:19 Skip http/ipv6_for_domain test when we have no ipv6 support [ Upstream commit 21477e40 ]
6f18f88e 2018-10-25 09:44:58 Remove for loop initial declaration and fix conflicting type in it (gcc 4.8) From [1]: regress_buffer.c:742:3: error: ‘for’ loop initial declarations are only allowed in C99 mode for (int i = 0; i < 1 << 16; ++i) { ^ regress_buffer.c:742:3: note: use option -std=c99 or -std=gnu99 to compile your code regress_buffer.c:787:23: error: conflicting types for ‘bufread’ for (int n = toread, bufread = toread; ^ regress_buffer.c:717:51: note: previous definition of ‘bufread’ was here size_t datalen = strlen(data), toread = datalen, bufread = 0; ^ regress_buffer.c:787:2: error: ‘for’ loop initial declarations are only allowed in C99 mode for (int n = toread, bufread = toread; ^ [1]: https://travis-ci.org/azat/libevent/jobs/445501665
b2beaad6 2018-10-24 01:18:41 Skip all dns tests that hit the network But since this version of tinytest do not have TT_OFF_BY_DEFAULT use TT_SKIP instead. [ Upstream commit f2cea873bb8c4e1e89cc282470a11556e4bd9730 ]
9e6f6503 2018-10-21 18:31:01 Simplify bufferevent timeout tests to reduce CPU usage in between start/compare [ Upstream commit 6ac8e775 ] [ Fixes: #262 ] Between start (setting "started_at") and comparing the time when timeouts triggered with the start (test_timeval_diff_eq), there is too much various things that can introduce extra delays and eventually could fail the test on machine with shortage of CPU. And this is exactly what happend on: - travis-ci - #262 Here is a simple reproducer that I came up with for this issue: docker run --cpus=0.01 -e LD_LIBRARY_PATH=$PWD/lib -e PATH=/usr/bin:/bin:$PWD/bin -v $PWD:$PWD --rm -it debian:testing regress --no-fork --verbose bufferevent/bufferevent_timeout Under limited CPU (see reproducer) the test almost always has problems with that "write_timeout_at" exceed default timeval diff tolerance (test_timeval_diff_eq() has 50 tolerance), i.e.: FAIL ../test/regress_bufferevent.c:1040: assert(labs(timeval_msec_diff(((&started_at)), ((&res1.write_timeout_at))) - (100)) <= 50): 101 vs 50 But under some setup write timeout can even not triggered, and the reason for this is that we write to the bufferevent 1024*1024 bytes, and hence if evbuffer_write_iovec() will has some delay after writev() and not send more then one vector at a time [1], it is pretty simple to trigger, i.e.: FAIL ../test/regress_bufferevent.c:1040: assert(labs(timeval_msec_diff(((&started_at)), ((&res1.write_timeout_at))) - (100)) <= 50): 1540155888478 vs 50 [1]: https://gist.github.com/azat/b72773dfe7549fed865d439e03de05c1 So this patch just send static small payload for all cases (plus a few more asserts added). The outcome of this patch is that all regression tests passed on travis-ci for linux box [2]. While before it fails almost always [3]. Also reproducer with CPU limiting via docker also survive some iterations (and strictly speaking it should has less CPU then travis-ci workers I guess). [2]: https://travis-ci.org/azat/libevent/builds/444391481 [3]: https://travis-ci.org/libevent/libevent/builds/444336505
dd3e841c 2017-12-18 01:02:25 Cover evbuffer_add_file() with offset
0091da36 2016-03-26 14:14:44 test/regress: add tests for evbuffer_add() breakage on empty last chain The evbuffer/add* tests currenly break on 2.0.21, 2.0.22 and 2.1 HEAD due to issue #335. The evbuffer/reference2 test breaks on 2.0.21 and 2.0.22 due to commit b18c04dd not being applied.