httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Hay <steve....@uk.radan.com>
Subject Re: [RELEASE CANDIDATE] libapreq2 2.08-RC3
Date Tue, 11 Jul 2006 08:56:25 GMT
Philip M. Gollucci wrote:
> Steve Hay wrote:
>> I still have an intermittent problem with one of the perl glue tests:
>> t\apreq\upload.t (I've mentioned this before when testing previous RC's).
> D'oh I swore that got fixed.
> 
>> [Tue Jul 11 09:39:27 2006] [error] [client 127.0.0.1] $param->upload_tempname($req):
can't make spool bucket at C:\\Temp\\libapreq2-2.08\\glue\\perl\\t\\response/TestApReq/upload.pm
line 33.\n
>> [Tue Jul 11 09:39:27 2006] [error] [client 127.0.0.1] The file exists.  
>> [Tue Jul 11 09:39:27 2006] [error] [client 127.0.0.1] (OS 80)The file exists.  :
apreq_brigade_concat failed; TempDir problem?
>> [Tue Jul 11 09:39:27 2006] [error] [client 127.0.0.1] The file exists.  
> 
> Do you mean just run make test in its entirety 6+ times, or have a running server and
run the test
> 6+ times without stopping the server in between.

I mean running the command:

C:\perl5mt\bin\perl.exe -Iblib\arch -Iblib\lib t/TEST -verbose=1 
t\apreq\upload.t

6 times or so in succession from the glue\perl sub-diretcory.  This, of 
course, kicks off a fresh server each time and stops it went it's done 
each time.

-- 


------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are confidential
and intended for the addressee(s) only. If you have received this message in error or there
are any problems, please notify the sender immediately. The unauthorized use, disclosure,
copying or alteration of this message is strictly forbidden. Note that any views or opinions
presented in this email are solely those of the author and do not necessarily represent those
of Radan Computational Ltd. The recipient(s) of this message should check it and any attached
files for viruses: Radan Computational will accept no liability for any damage caused by any
virus transmitted by this email.
Mime
View raw message