Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re: How do track down underlying reason for smoke test failure

by marto (Archbishop)
on Sep 12, 2019 at 09:38 UTC ( #11106054=note: print w/replies, xml ) Need Help??


in reply to How do track down underlying reason for smoke test failure

"Do I set up a perl distro with the same exact module config..."

Since your module is on github you can add Continuous_integration via Travis_CI with very little effort, and no financial cost, have it test your code against several versions of perl, on different OS etc. Create your .travis.yml (or see Travis-CI Helpers for Perl), setup Travis CI, activate the repos and it'll do it automatically from then on.

  • Comment on Re: How do track down underlying reason for smoke test failure

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://11106054]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (3)
As of 2019-10-14 00:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Notices?