On 09/19/2017 01:31 PM, Andres Freund wrote: > Hi, > > I've had a couple cases where tap tests died, and I couldn't easily see > where / why. For development of a new test I found it useful to show > backtraces in that case - just adding a > use Carp::Always; > at the start of the relevant module did the trick. > > I'm wondering if we shouldn't always do so if the module is > installed. I.e. have PostgresNode or something do something like > > # Include module showing backtraces upon failures. As it's a > non-standard module, don't fail if not installed. > eval { use Carp::Always; } > > Comments? >
Or maybe Devel::Confess ? In an eval you need a 'require' rather than a 'use', AFAIK. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers