Also, if you do this, make sure you use a recent version of Test::Harness that supports a rules file to hint about what can run in parallel.
Search TAP::Harness docs for "rules" and you'll find it. An example is here: https://github.com/mongodb/mongo-perl-driver/blob/master/t/testrules.yml As long as you're running a new enough Test::Harness, authors can "fix" their tests by dropping in a rules files that requires some (or all)things to run serially. It's not well documented in the community, which is too bad. I keep meaning to blog about it but haven't gotten around to it yet. David On Sun, Oct 25, 2015 at 10:03 PM, Alceu R. de Freitas Jr. < glasswal...@yahoo.com.br> wrote: > Hi again, > > I was doing some research to see if there is any way to improve smoker > performance by using parallelism. I found this article on > http://modernperlbooks.com/mt/2011/11/parallelism-and-test-suites.html > that discuss some issues when trying to do something like that. > > Interesting as is, is there any feature to mark the tests results from a > distribution that was executed with parallelism? That could help the > authors to identify issues with their tests when running with parallelism. > Maybe we could even mark (in Metacpan) the distribution as capable to be > tested with parallelism. > > Or maybe the distribution author could explicit ask to not test the > distribution with parallelism. > > Anyway, I just brainstorming here, no patches available right now. :-) > > Regards, > > Alceu > > -- David Golden <x...@xdg.me> Twitter/IRC/Github: @xdg
