Proof-of-concept for `prove -j 4 --serial-tests=FILE` #3

Closed
wants to merge 5 commits into
from

Conversation

Projects
None yet
1 participant
Contributor

markstos commented Aug 17, 2012

It allows you to run most tests of a test suite in parallel, while
specifying a file which lists tests which are not yet parallel-safe.

There are no automated tests yet, but it manually tests well enough on the Test::Harness test suite, including all-serial runs, all-parallel runs, and using the new flag for a hybrid serial/parallel run.

What do you think?

Since it doesn't disturb existing functionality, I thought it was a good candidate for sharing an experimental feature that might change or be removed. I imagine there are number of folks like me who would like to take advantage of parallel test runs, but have held back because their test suite is not 100% parallel-ready.

markstos added some commits Aug 17, 2012

Proof-of-concept for `prove -j 4 --serial-tests=FILE`
    It allows you to run *most* tests of a test suite in parallel, while
    specifying a file which lists tests which are not yet parallel-safe.
Contributor

markstos commented Aug 17, 2012

Further testing found a bug. Revising and re-testing now.

Contributor

markstos commented Aug 17, 2012

Hmm. now I just found the 'rules' directive in TAP::Harness, which appears to be an alternate approach to address the same goal. I'll have to investigate that.

Contributor

markstos commented Aug 17, 2012

Any history of about the 'rules' directive would be welcome to hear. So far I can see that it was added to prove in 3.13 around 2008, but it was never documented in prove an an option, or exactly what syntax should be used to drive it.

There was a discussion thread about it here in 2009, discussing having a "rules file" instead of or in addition using command-line flags to drive it.

http://www.nntp.perl.org/group/perl.qa/2009/03/msg12074.html

Now I'm going to see if I can figure out how to what I want our test suite using the undocumented --rules option.

Contributor

markstos commented Aug 17, 2012

I pushed a fix for that bug, I still don't a summary report at the end of my run. The same thing happens when I try the undocumented --rules command. I'm continuing the discussion about this feature on the Perl QA list. A link to that thread should be appearing here shortly:

http://www.nntp.perl.org/group/perl.qa/2012/08.html

@markstos markstos closed this Aug 18, 2012

Contributor

markstos commented Aug 18, 2012

I found a the built-in but undocumented way to solve the same problem with the Scheduler and the rules system. I'm going to pursue documenting that instead, so I'm closing this Pull Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment