From: Peter Rabbitson Date: Wed, 16 Oct 2013 03:56:39 +0000 (+0200) Subject: Smoother concurrent test-flow X-Git-Tag: v0.08260~109 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=39568b8ae8bbe3cf6b6873ce87a8fd925a539d64;p=dbsrgits%2FDBIx-Class.git Smoother concurrent test-flow The noop trick initializes the STDOUT, so that the TAP::Harness issued IO::Select->can_read calls (which are blocking wtf wtf wtf) keep spinning and scheduling jobs This results in an overall much smoother job-queue drainage, since the Harness blocks less (ideally this needs to be addressed in T::H, but a quick patchjob broke everything so tabling it for now) --- diff --git a/t/lib/DBICTest.pm b/t/lib/DBICTest.pm index 42a691b..a185763 100644 --- a/t/lib/DBICTest.pm +++ b/t/lib/DBICTest.pm @@ -3,6 +3,21 @@ package # hide from PAUSE use strict; use warnings; + +# this noop trick initializes the STDOUT, so that the TAP::Harness +# issued IO::Select->can_read calls (which are blocking wtf wtf wtf) +# keep spinning and scheduling jobs +# This results in an overall much smoother job-queue drainage, since +# the Harness blocks less +# (ideally this needs to be addressed in T::H, but a quick patchjob +# broke everything so tabling it for now) +BEGIN { + if ($INC{'Test/Builder.pm'}) { + local $| = 1; + print "#\n"; + } +} + use DBICTest::RunMode; use DBICTest::Schema; use DBICTest::Util::LeakTracer qw/populate_weakregistry assert_empty_weakregistry/;