Skip Menu |

This queue is for tickets about the POE-Component-Client-HTTP CPAN distribution.

Report information
The Basics
Id: 41278
Status: resolved
Priority: 0/
Queue: POE-Component-Client-HTTP

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.86
Fixed in: (no value)



Subject: t/01_request fails
My smoker started to fail on t/01_request.t. When running verbose I get: t/01_request.... 1..13 ok 1 - got 400 response for request with unsupported scheme ok 2 - got 500 response for request on bad host ok 3 - got test request we will let timeout ok 4 - got test request ok 5 - got post request with content ok 6 - sending too much data as requested ok 7 - got 200 response for post request ok 8 - got 200 response for test request ok 9 - got 400 response for long request ok 10 - got 408 response for timed out request not ok 11 - unexpected response # Failed test 'unexpected response' # at t/01_request.t line 170. # path(/post2) code(408) # response((( # 408 Request Timeout # # <html> # <HEAD><TITLE>Error: Request Timeout</TITLE></HEAD> # <BODY> # <H1>Error: Request Timeout</H1> # Request timed out # </BODY> # </HTML> # ))) # Looks like you planned 13 tests but ran 11. # Looks like you failed 1 test of 11 run. Dubious, test returned 1 (wstat 256, 0x100) Failed 3/13 subtests Test Summary Report ------------------- t/01_request (Wstat: 256 Tests: 11 Failed: 1) Failed test: 11 Non-zero exit status: 1 Parse errors: Bad plan. You planned 13 tests but ran 11. Files=1, Tests=11, 4 wallclock secs ( 0.06 usr 0.01 sys + 0.50 cusr 0.09 csys = 0.66 CPU) Result: FAIL perls are recent bleadperls you should have received some reports from my smoker. Let me know whether I can provide more informations. Best,
Hi, Andreas. It appears that the 1sec timeout was too short. I've seen sporadic timeouts here as well. I've committed revision 358 which sets the timeout to 3sec. It will be so in the next release. Please reopen the ticket or create a new one if the problem continues after the next release. Thank you!