Re: perl test framework

2017-07-05 Thread Jim Jagielski 
Ok... was just making sure it wasn't just me having issues
with more modern Perls.

Re: perl test framework

2017-07-05 Thread Eric Covener 
On Wed, Jul 5, 2017 at 12:04 PM, Jacob Champion  wrote:
> 5.22.1, as distributed with Ubuntu 16.04 (plenty of Debian patches).

Same here. For a release I usually run on my AIX systems 5.10.1 with
some CPAN additions/upgrades to be able to get H2 to work. But, I
think it has started to get a little flakey on some old SSL tests.

-- 
Eric Covener
cove...@gmail.com

Re: perl test framework

2017-07-05 Thread Jacob Champion 

On 07/05/2017 04:01 AM, Jim Jagielski wrote:

I am curious... what versions of Perl are people using
when running the Perl test framework? It seems that, at least
to me, it is quite picky regarding versions, at least on
macOS.


5.22.1, as distributed with Ubuntu 16.04 (plenty of Debian patches).

--Jacob

Re: perl test framework

2017-07-05 Thread Jim Jagielski 

> On Jul 5, 2017, at 8:39 AM, Rainer Jung  wrote:
> 
> Solaris: self-compiled 5.22.0

I have found that 5.20.x works best for me... I have also
found that doing a universal CPAN update generally causes
various framework tests to fail[1]; usually the 1st hint of
troubles are that the byterange tests just spin and spin.


1. I just cpan install as needed and use whatever versions
   are noted in the Bundle::ApacheTest and do NOT upgrade
   things like Test::Harness, etc...

Re: perl test framework

2017-07-05 Thread Rainer Jung 

Am 05.07.2017 um 13:01 schrieb Jim Jagielski:

I am curious... what versions of Perl are people using
when running the Perl test framework? It seems that, at least
to me, it is quite picky regarding versions, at least on
macOS.


Just my personal recipe:

Solaris: self-compiled 5.22.0
Linux: Platform perl for RHEL 6+7, SLES 11+12.

But even for the platform perl I add a lot of self-compiled and 
separately installed modules to make sure I have relatively recent ones. 
The list of those modules is very close to what we included in the 
framework README.


Picking up those modules works using the PERL5LIB variable, installing 
into the separate directory (here named /instdir) is based on the 
following env vars:


export PERL5LIB="/instdir/perl5"
export PERL_MB_OPT="--install_base /instdir"
export PERL_MM_OPT="INSTALL_BASE=/instdir"
export PERL_LOCAL_LIB_ROOT="/instdir"

I also add /instdir/bin to the PATH and I then install the modules using 
CPAN and starting with


install local::lib

Regards,

Rainer