[Catalyst-dev] CATALYST_DEBUG=0 weirdness

Kieren Diment diment at gmail.com
Tue Apr 21 13:07:02 GMT 2009


Something odd going on here.  CATALYST_DEBUG=0 prove -l t still has  
debugging output when -Debug is set but the env var is 0.  This is  
different from the 5.7 behaviour.  The test in the minimal app  
attached fails on 5.8 and passes on 5.7.  Apologies it's an evil test  
with backticks rather than something proper for folding straight into  
the -runtime codebase, I'm not sure how I would do that right given  
the need to capture stderr, also the easiest way for me to ge the  
desired output is to run script/myapp_test / , so I figured I'd leave  
making it a real test to the experts.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: DebugFail.tar.gz
Type: application/x-gzip
Size: 41057 bytes
Desc: not available
Url : http://lists.scsys.co.uk/pipermail/catalyst-dev/attachments/20090421/b7b7197e/DebugFail.tar-0001.bin
-------------- next part --------------




More information about the Catalyst-dev mailing list