Hello there, I've see errors reported from my distribution for situations that seems to me are related to concurrent tests execution (I'm always getting those from ANDK): "# Failed test 'runs died (Previous executing is still running (PID 12133), cannot execute at /tmp/loop_over_bdir-28064-2H5GAD/Siebel-Srvrmgr-0.18-TisEJS/blib/lib/Siebel/Srvrmgr/Daemon.pm line 933)'# at t/DaemonHeavy.t line 4.# (in Test::Siebel::Srvrmgr::Daemon::Heavy->runs)" http://www.cpantesters.org/cpan/report/b329e604-24e6-11e5-80c9-e5781ad7484d The distribution has code to control concurrent execution of the same module code (it dies when that is detected). The test suite also includes a test with dies_ok for this kind of situation, but the exception raised in these reported failures are legit. Meanwhile I could trap those exceptions and skip the rest of the tests, I'm basically avoiding those tests to be executed. Did you had such situations in the past and could share your experience with it? I'm not sure the best approach to avoid those failures. Maybe executing the tests under eval, inside a while loop and sleeping for a random number of seconds?
Thanks,Alceu
