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.
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.
Attached Files:
-
DebugFail.tar.gz (40.1 KB)