[Catalyst] Using Test::Log4perl, testing cat log output only works after firing initial request

[Sebastian Willert]

On Mon, 2009-03-23 at 15:22 +0000, Tomas Doran wrote:
> Anthony Gladdish wrote:
> > Has anyone else experienced this problem? 
> > Should this be happening in this way and is there a fix or workaround?
> >
> > I'm trying to test and iron this out prior to rolling out into production.
> >   
> I certainly haven't seen this sort of behavior in my applications.
> 
> Can you try reducing the behavior that you're seeing to a test case for 
> the Catalyst::Log::Log4perl distribution?

And here are your test cases (against C::L::Log4perl 1.03 and Log4perl
1.20). Unfortunately it seems like we can't do anything about this on
our side ...

Cheers,
  Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20-test-log4perl.t
Type: text/troff
Size: 718 bytes
Desc: not available
Url : http://lists.scsys.co.uk/pipermail/catalyst/attachments/20090324/592cdca4/20-test-log4perl.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 21-test-log4perl-hotfix.t
Type: text/troff
Size: 582 bytes
Desc: not available
Url : http://lists.scsys.co.uk/pipermail/catalyst/attachments/20090324/592cdca4/21-test-log4perl-hotfix.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 22-test-log4perl-hotfix-broken.t
Type: text/troff
Size: 764 bytes
Desc: not available
Url : http://lists.scsys.co.uk/pipermail/catalyst/attachments/20090324/592cdca4/22-test-log4perl-hotfix-broken.bin