I managed to submit two reports without any errors than I got the same
result as James Keenan.

TAP Archive created at /home/mhu/t.parrot/parrot_test_run.tar.gz
Could not upload report to Smolder at http://smolder.plusthree.com
HTTP CODE: 500 (read timeout)
make: *** [smolder_test] Error 255

I went to the site:
http://smolder.plusthree.com/app/projects/smoke_reports/8

This was showing a empty report - #31520 (unknown, and all 0's) I then did a
refresh and it then had #31520 as my submission.

So this seems to indicate that the 500 code (read timeout) was sent by the
server before the submission was complete, but the submission was eventually
completed.

I am not sure where the timeout is set (client side or more probably server
side) but maybe this needs looking into.

Cheers Michael (mikehh)


2010/1/7 James E Keenan <[email protected]>

> Michael Peters wrote:
>
>> On 01/06/2010 08:29 AM, Andrew Whitworth wrote:
>>
>
>
>> See if this attached patch fixes things.
>>
>>
> I saw that a patch was applied today.  Nonetheless, even after 'make
> realclean;perl Configure.pl;make;make smoke', I could not get the right
> feedback on the upload.
>
> TAP Archive created at /home/jimk/work/parrot/parrot_test_run.tar.gz
>
> Could not upload report to Smolder at http://smolder.plusthree.com
> HTTP CODE: 500 (read timeout)
> make: *** [smolder_test] Error 255
> Finished
>
> The report did upload:
> http://smolder.plusthree.com/app/projects/report_details/31512
>
>
> kid51
>
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>



-- 
Michael H. Hind

Tel:  +44 (0) 1224 631 581
Cell: +44 (0) 7877 224 745
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev

Reply via email to