Re: [PATCH] always multi v5
Date: Wed, 23 Jan 2013 11:51:10 -0700
On Jan 21, 2013, at 6:33 PM, Nick Zitzmann <nick_at_chronosnet.com> wrote:
> But it started happening once the change was made; that test used to pass. Would it help if I ran all tests and then submitted what was logged prior to the stall?
Well, I did it anyway, and according to trace254 it appears that after some recent changes, curl can no longer interpret the response to an FTP request to enter passive mode on my system:
> 0000: 227 Entering Passive Mode (::1,246,130).
> 11:36:36.937919 == Info: Couldn't interpret the 227-response
And test 255 gets up to this point and then stalls:
> 11:36:47.008582 => Send header, 5 bytes (0x5)
> 0000: PWD
> 11:36:47.008595 == Info: FTP 0x7f9abb0118e8 (line 857) state change from PASS to PWD
> 11:36:47.010172 <= Recv header, 30 bytes (0x1e)
> 0000: 257 "/" is current directory
So could the person responsible for FTP look into these? Here's the contents of my log folder at the time of the stall in test 255.
- application/x-gzip attachment: logs254-255.tar.gz