Nicholas Clark wrote:

On Thu, Sep 22, 2005 at 10:37:00PM +0100, Steve Hay wrote:
  25572     Configuration (common) -DINST_TOP=$(INST_DRV)\Smoke\doesntexist
----------- ---------------------------------------------------------
O O O O -Dusemymalloc
O O         -Duselargefiles
O O         -Duselargefiles -Dusemymalloc
O O         -Duseithreads -Uuseimpsys
O O         -Duseithreads -Uuseimpsys -Dusemymalloc
O O         -Duseithreads -Uuseimpsys -Duselargefiles
O O         -Duseithreads -Uuseimpsys -Duselargefiles -Dusemymalloc
O O         -Duseithreads
O O         -Duseithreads -Duselargefiles
| +--------- -DDEBUGGING
+----------- no debugging

Gosh. What did I do wrong?

I even hand merged the win32 config files, and still it seems that I didn't
mess up this time. Must try harder.
Thanks for that. I did spot one slip, though -- half the comment is missing at line 3424 in config_H.vc64.

While I was checking things I also noticed that my change 25226 only did half the job. This is corrected in 25573, which should also be integrated to maint.

What cause the threads problem test to pass tonight, when it failed last night?
Or will we never know?

The latter, I'm afraid. I suspect it is just "one of those things". The blead smokes still occasionally fail this test, and I expect that the maint smokes will continue to do so occasionally too.

Jan has seen this problem too and thought that it looked like a race condition, hence the intermittent nature of it:

http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2004-05/msg00443.html



------------------------------------------------
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.

Reply via email to