[Cppcms-users] cppcms 1.1.0 Build failed test "http_timeouts_test_write"
Brought to you by:
artyom-beilis
|
From: Ramakrishna M. <ram...@gm...> - 2013-11-24 09:40:34
|
Hi Everyone,
I have downloaded the latest code version "1.1.0" from svn and it build
without any errors, and while running "make test" out of 97 only 1 test
failed i.e "http_timeouts_test_write".
Please find the test log below.
"
2013-11-24 11:52:40; cppcms_http, info: GET /async/long (http_api.cpp:251)
2013-11-24 11:52:46; cppcms_http, info: Timeout on connection for URI:
/async/long from 127.0.0.1 (http_api.cpp:172)
2013-11-24 11:52:46; cppcms, warning: Writing response failed:aio:::
canceled (cgi_api.cpp:493)
2013-11-24 11:52:50; cppcms_http, info: GET /async/long (http_api.cpp:251)
2013-11-24 11:52:56; cppcms_http, info: Timeout on connection for URI:
/async/long from 127.0.0.1 (http_api.cpp:172)
2013-11-24 11:52:56; cppcms, warning: Writing response failed:aio:::
canceled (cgi_api.cpp:493)
File "/home/web/cppcms/tests/http_timeouts_test.py", line 76, in <module>
test_unfinished_read('GET /async/long HTTP/1.0',20,1000)
File "/home/web/cppcms/tests/http_timeouts_test.py", line 58, in
test_unfinished_read
test(l > 0)
File "/home/web/cppcms/tests/http_timeouts_test.py", line 16, in test
traceback.print_stack()
Write to the client timeout
Tesing GET /async/long HTTP/1.0 with 0 reads
SO_RCVBUF=262006
Tesing GET /async/long HTTP/1.0 with 20 reads
SO_RCVBUF=262006
Error
Statistics:
sync_bad_count =0
async_bad_count =2
count_timeouts =2
above 15 =0
below 10 =2
eof =0
Failed
<end of output>
Test time = 28.11 sec
----------------------------------------------------------
Test Failed.
"http_timeouts_test_write" end time: Nov 24 11:53 IST
"http_timeouts_test_write" time elapsed: 00:00:28
----------------------------------------------------------
"
Does anyone have this issue earlier.
My System configuration:
ubuntu 12.04.3 LTS and g++ 4.7.3
What are the difference between the Released version [1.0.4] and version
[1.1.0].
Before this I have compiled & run the tests of the release version [1.0.4]
without any issues.
Thanks
Ram
|