Looks to be resolved in v16. Though your tests have uncovered another issue with my module. Namely, Term::ANSIColor not exporting a function I'm using. Have added an issue on my github tracker, and will look at fixing for v17.
https://github.com/teodesian/TestRail-Perl/issues/20
Thanks again for the heads up, and the smoking of my module!
On Mon Jan 26 10:02:57 2015, TEODESIAN wrote:
Show quoted text> Thank you! Having never looked into how the smokers were actually
> doing things, I was flat out at a loss as to why some of these
> failures were happening. None of them made any sense, unless there
> are incompatible perls being used.
>
> Will use $^X going forward.
>
> Once again, thanks. I think I'll look into running my own smoking
> server in the future just to familiarize myself with things (and to
> have ability to reproduce such in the future).
>
> On Mon Jan 26 02:01:44 2015, SREZIC wrote:
> > The testrail-report invocations in t/testrail-report.t use the system
> > perl and not the perl currently tested for (unless the user adjusted
> > PATH). This probably explains the many fail reports on cpantesters.
> > My
> > suggestions:
> >
> > - explicitly use the currently used perl, e.g. by using something
> > like
> >
> > my @args = ($^X, qw{bin/testrail-report ...));
> >
> > - or replace the shebang in testrail-report by !#perl or
> > #!/usr/bin/perl, and use the version installed in blib/scripts for
> > testing (where the shebang is already adjusted) (though this won't
> > work under Windows)
