From @eserte

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.40 running under perl 5.25.11.

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie, Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

Flags​:
  category=core
  severity=low

Site configuration information for perl 5.25.11​:

Configured by eserte at Mon Mar 20 21​:18​:52 UTC 2017.

Summary of my perl5 (revision 5 version 25 subversion 11) configuration​:
 
  Platform​:
  osname=linux
  osvers=3.16.0-4-amd64
  archname=x86_64-linux
  uname='linux eserte 3.16.0-4-amd64 #1 smp debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 gnulinux '
  config_args='-ds -e -Dprefix=/opt/perl-5.25.11 -Dusedevel -Dusemallocwrap=no -Dcf_email=srezic@​cpan.org'
  hint=recommended
  useposix=true
  d_sigaction=define
  useithreads=undef
  usemultiplicity=undef
  use64bitint=define
  use64bitall=define
  uselongdouble=undef
  usemymalloc=n
  default_inc_excludes_dot=define
  bincompat5005=undef
  Compiler​:
  cc='cc'
  ccflags ='-fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2'
  optimize='-O2'
  cppflags='-fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include'
  ccversion=''
  gccversion='4.9.2'
  gccosandvers=''
  intsize=4
  longsize=8
  ptrsize=8
  doublesize=8
  byteorder=12345678
  doublekind=3
  d_longlong=define
  longlongsize=8
  d_longdbl=define
  longdblsize=16
  longdblkind=3
  ivtype='long'
  ivsize=8
  nvtype='double'
  nvsize=8
  Off_t='off_t'
  lseeksize=8
  alignbytes=8
  prototype=define
  Linker and Libraries​:
  ld='cc'
  ldflags =' -fstack-protector-strong -L/usr/local/lib'
  libpth=/usr/local/lib /usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed /usr/include/x86_64-linux-gnu /usr/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib
  libs=-lpthread -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc -lgdbm_compat
  perllibs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
  libc=libc-2.19.so
  so=so
  useshrplib=false
  libperl=libperl.a
  gnulibc_version='2.19'
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs
  dlext=so
  d_dlsymun=undef
  ccdlflags='-Wl,-E'
  cccdlflags='-fPIC'
  lddlflags='-shared -O2 -L/usr/local/lib -fstack-protector-strong'

@​INC for perl 5.25.11​:
  lib
  /opt/perl-5.25.11/lib/site_perl/5.25.11/x86_64-linux
  /opt/perl-5.25.11/lib/site_perl/5.25.11
  /opt/perl-5.25.11/lib/5.25.11/x86_64-linux
  /opt/perl-5.25.11/lib/5.25.11

Environment for perl 5.25.11​:
  HOME=/home/eserte
  LANG=C
  LANGUAGE (unset)
  LD_LIBRARY_PATH (unset)
  LOGDIR (unset)
  PATH=/usr/local/bin​:/usr/bin​:/bin​:/usr/local/sbin​:/usr/sbin​:/sbin​:/home/eserte/bin/linux-gnu​:/home/eserte/bin/sh​:/home/eserte/bin​:/home/eserte/bin/pistachio-perl/bin​:/usr/games​:/home/eserte/devel
  PERLDOC=-MPod​::Perldoc​::ToTextOverstrike
  PERL_BADLANG (unset)
  SHELL=/bin/zsh

From @jkeenan

On Tue, 21 Mar 2017 18​:58​:50 GMT, slaven@​rezic.de wrote​:

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.40 running under perl 5.25.11.

-----------------------------------------------------------------
t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl
line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok
1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

Have you been able to identify the commit at which this first appears?

Thank you very much.
--
James E Keenan (jkeenan@​cpan.org)

The RT System itself - Status changed from 'new' to 'open'

From @eserte

Dana Tue, 21 Mar 2017 12​:59​:58 -0700, jkeenan reče​:

On Tue, 21 Mar 2017 18​:58​:50 GMT, slaven@​rezic.de wrote​:

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.40 running under perl 5.25.11.

-----------------------------------------------------------------
t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl
line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok
1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

Have you been able to identify the commit at which this first appears?

Thank you very much.

The problematic test was merged just one week ago, so probably it always failed on my systems.

From @jkeenan

On Tue, 21 Mar 2017 20​:13​:31 GMT, slaven@​rezic.de wrote​:

Dana Tue, 21 Mar 2017 12​:59​:58 -0700, jkeenan reče​:

On Tue, 21 Mar 2017 18​:58​:50 GMT, slaven@​rezic.de wrote​:

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.40 running under perl 5.25.11.

-----------------------------------------------------------------
t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at
./test.pl
line 1071
# got 'Out of memory!'
# expected
/(?^​:\Aok
1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

Have you been able to identify the commit at which this first
appears?

Thank you very much.

The problematic test was merged just one week ago, so probably it
always failed on my systems.

I guess you mean​:

#####
commit a7dd840
Author​: David Mitchell <davem@​iabyn.com>
AuthorDate​: Tue Mar 7 15​:22​:49 2017 +0000
Commit​: David Mitchell <davem@​iabyn.com>
CommitDate​: Wed Mar 15 09​:19​:54 2017 +0000

  add range.t test for RT #130841
#####

Dave M, can you take a look at this?

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

From @jkeenan

On Tue, 21 Mar 2017 21​:37​:12 GMT, jkeenan wrote​:

On Tue, 21 Mar 2017 20​:13​:31 GMT, slaven@​rezic.de wrote​:

Dana Tue, 21 Mar 2017 12​:59​:58 -0700, jkeenan reče​:

On Tue, 21 Mar 2017 18​:58​:50 GMT, slaven@​rezic.de wrote​:

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.40 running under perl 5.25.11.

-----------------------------------------------------------------
t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at
./test.pl
line 1071
# got 'Out of memory!'
# expected
/(?^​:\Aok
1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

Have you been able to identify the commit at which this first
appears?

Thank you very much.

The problematic test was merged just one week ago, so probably it
always failed on my systems.

I guess you mean​:

#####
commit a7dd840
Author​: David Mitchell <davem@​iabyn.com>
AuthorDate​: Tue Mar 7 15​:22​:49 2017 +0000
Commit​: David Mitchell <davem@​iabyn.com>
CommitDate​: Wed Mar 15 09​:19​:54 2017 +0000

add range\.t test for RT \#130841

#####

Dave M, can you take a look at this?

Thank you very much.

Dave Mitchell​: RT #130841 is inaccessible. When I got to https://rt-archive.perl.org/perl5/Ticket/Display.html?id=130841, I get "RT Error No permission to view ticket"

--
James E Keenan (jkeenan@​cpan.org)

From @iabyn

On Tue, Mar 21, 2017 at 11​:58​:51AM -0700, slaven@​rezic.de wrote​:

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie, Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

What commonalities and variations are there between the platforms?
Especially on pointer and int size, and whether they were all built with
options like -Dusemallocwrap=no?

--
O Unicef Clearasil!
Gibberish and Drivel!
  -- "Bored of the Rings"

From @eserte

Dana Wed, 22 Mar 2017 00​:38​:10 -0700, davem reče​:

On Tue, Mar 21, 2017 at 11​:58​:51AM -0700, slaven@​rezic.de wrote​:

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie, Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

What commonalities and variations are there between the platforms?
Especially on pointer and int size, and whether they were all built with
options like -Dusemallocwrap=no?

All have -Dusemallocwrap=no set. All are 64bit systems, probably with similar config output as the listed one.

From @eserte

Dana Wed, 22 Mar 2017 00​:46​:23 -0700, slaven@​rezic.de reče​:

Dana Wed, 22 Mar 2017 00​:38​:10 -0700, davem reče​:

On Tue, Mar 21, 2017 at 11​:58​:51AM -0700, slaven@​rezic.de wrote​:

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at
./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1
ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

What commonalities and variations are there between the platforms?
Especially on pointer and int size, and whether they were all built
with
options like -Dusemallocwrap=no?

All have -Dusemallocwrap=no set. All are 64bit systems, probably with
similar config output as the listed one.

The test passes if -Dusemallocwrap=no is not set (at least on one system).

From @iabyn

On Wed, Mar 22, 2017 at 12​:46​:23AM -0700, slaven@​rezic.de via RT wrote​:

Dana Wed, 22 Mar 2017 00​:38​:10 -0700, davem reče​:

On Tue, Mar 21, 2017 at 11​:58​:51AM -0700, slaven@​rezic.de wrote​:

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at ./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1 ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie, Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

What commonalities and variations are there between the platforms?
Especially on pointer and int size, and whether they were all built with
options like -Dusemallocwrap=no?

All have -Dusemallocwrap=no set. All are 64bit systems, probably with
similar config output as the listed one.

I've just pushed the following, which hopefully should fix it for you.

commit 2d5eff8
Author​: David Mitchell <davem@​iabyn.com>
AuthorDate​: Wed Mar 22 08​:35​:33 2017 +0000
Commit​: David Mitchell <davem@​iabyn.com>
CommitDate​: Wed Mar 22 08​:35​:33 2017 +0000

  skip an op/range.t test under -Dusemallocwrap=no
 
  RT #131033
 
  A recently added test checked for a memory wrap condition, which won't
  happen if memory wrap checking is disabled.

--
Counsellor Troi states something other than the blindingly obvious.
  -- Things That Never Happen in "Star Trek" #16

From @eserte

Dana Wed, 22 Mar 2017 01​:41​:14 -0700, davem reče​:

On Wed, Mar 22, 2017 at 12​:46​:23AM -0700, slaven@​rezic.de via RT
wrote​:

Dana Wed, 22 Mar 2017 00​:38​:10 -0700, davem reče​:

On Tue, Mar 21, 2017 at 11​:58​:51AM -0700, slaven@​rezic.de wrote​:

t/op/range.t fails for me​:

$ ./perl -Ilib t/op/range.t
...
not ok 146 - RT \#130841
# Failed test 146 - RT \#130841 at
./test.pl line 1071
# got 'Out of memory!'
# expected /(?^​:\Aok 1
ok 2\Z)/
...

This happens on several platforms​: linux (Debian/jessie,
Debian/stretch,
Ubuntu 16.04, CentOS7) and freebsd (10.3).

What commonalities and variations are there between the platforms?
Especially on pointer and int size, and whether they were all built
with
options like -Dusemallocwrap=no?

All have -Dusemallocwrap=no set. All are 64bit systems, probably with
similar config output as the listed one.

I've just pushed the following, which hopefully should fix it for you.

commit 2d5eff8
Author​: David Mitchell <davem@​iabyn.com>
AuthorDate​: Wed Mar 22 08​:35​:33 2017 +0000
Commit​: David Mitchell <davem@​iabyn.com>
CommitDate​: Wed Mar 22 08​:35​:33 2017 +0000

skip an op/range.t test under -Dusemallocwrap=no

RT #131033

A recently added test checked for a memory wrap condition, which won't
happen if memory wrap checking is disabled.

Confirmed, I have a green build with this commit​: https://travis-ci.org/eserte/perl5/builds/213962164

From @jkeenan

Patch applied and satisfies OP's concerns. Marking ticket Resolved.
--
James E Keenan (jkeenan@​cpan.org)

@jkeenan - Status changed from 'open' to 'resolved'