Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <420808C4.7000705@stason.org>
Date: Mon, 07 Feb 2005 19:33:08 -0500
From: Stas Bekman <stas@stason.org>
Organization: Hope, Humanized
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
MIME-Version: 1.0
To: Steve Hay <steve.hay@uk.radan.com>
Cc: dev@perl.apache.org
Subject: Re: New ModPerl-Registry/t/ithreads.t test fails on Win32
References: <4207A7B7.5050503@uk.radan.com>
In-Reply-To: <4207A7B7.5050503@uk.radan.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Steve Hay wrote:
> What is it with tests called "ithreads.t"?

it's a forbidden word :)

> # expected: thread 1
> # thread 2
> # thread 3
> # thread 4
> # parent
> # received: thread 1
> # thread 2
> # thread 3
> # parent
> not ok 1
> FAILED test 1
>         Failed 1/1 tests, 0.00% okay
> Failed Test  Stat Wstat Total Fail  Failed  List of Failed
> -------------------------------------------------------------------------------
> t\ithreads.t                1    1 100.00%  1
> Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
> [warning] server localhost:8529 shutdown
> [  error] error running tests (please examine t\logs\error_log)
> 
> I don't understand what happened to thread 4 :(

most likely the thing that I've suggested in reply to Joe. By the time it 
sent its print the parent has returned. Try to add sleep 2 before print 
'parent'. Does it fix the problem (notice that I've committed a change).

If so then once I figure out what those leak reports are, the join() 
blocking will fix it w/o sleep.

> Also, why are there comments in 
> ModPerl-Registry/t/cgi-bin/ithreads_io_n_tie.pl about $thr->join leaking 
> scalars in this new test but not in the non-registry tests?  I believe 
> that the non-registry tests also leak scalars. 

only were randomly on linux and only on destroy.

> It is precisely warnings 
> about such things that causes the non-registry ithreads.t test to fail 
> for me (by virtue of the "use warnings FATAL => 'all';" line).

yeah, I had little time when I wrote this test and my objective was to 
find workarounds to the perl_clone+perlio bug in perl, not deal with 
perl's ithreads bugs :) but I plan to revisit that when I will finish my 
other short term todo lists. 5.6.7 should be out in a month, so we may 
need to shake that threads thingy again before that happens.


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org