Bleadperl v5.27.5-387-g006c1a1dbd breaks RKINYON/DBM-Deep-2.0014.tar.gz #16276

p5pRT · 2017-11-23T21:08:22Z

Migrated from rt.perl.org#132493 (status was 'resolved')

Searchable as RT132493$

p5pRT · 2017-11-23T21:08:23Z

From @andk

bisect

commit 006c1a1 (HEAD, refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics

http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat 65280, 0xff00)
All 11 subtests passed

perl -V

Summary of my perl5 (revision 5 version 27 subversion 6) configuration:
Commit id: 006c1a1
Platform:
osname=linux
osvers=4.12.0-2-amd64
archname=x86_64-linux
uname='linux k93msid 4.12.0-2-amd64 #1 smp debian 4.12.13-1 (2017-09-19) x86_64 gnulinux '
config_args='-Dprefix=/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.27.5-387-g006c1a1dbd/da1c -Dmyhostname=k93msid -Dinstallusrbinperl=n -Uversiononly -Dusedevel -des -Ui_db -Dlibswanted=cl pthread socket inet nsl gdbm dbm malloc dl ld sun m crypt sec util c cposix posix ucb BSD gdbm_compat -Uuseithreads -Uuselongdouble -DEBUGGING=-g'
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 -g'
cppflags='-fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include'
ccversion=''
gccversion='7.2.0'
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/7/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 -ldl -lm -lcrypt -lutil -lc
perllibs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
libc=libc-2.24.so
so=so
useshrplib=false
libperl=libperl.a
gnulibc_version='2.24'
Dynamic Linking:
dlsrc=dl_dlopen.xs
dlext=so
d_dlsymun=undef
ccdlflags='-Wl,-E'
cccdlflags='-fPIC'
lddlflags='-shared -O2 -g -L/usr/local/lib -fstack-protector-strong'

Characteristics of this binary (from libperl):
Compile-time options:
HAS_TIMES
PERLIO_LAYERS
PERL_COPY_ON_WRITE
PERL_DONT_CREATE_GVSV
PERL_MALLOC_WRAP
PERL_OP_PARENT
PERL_PRESERVE_IVUV
PERL_USE_DEVEL
USE_64_BIT_ALL
USE_64_BIT_INT
USE_LARGE_FILES
USE_LOCALE
USE_LOCALE_COLLATE
USE_LOCALE_CTYPE
USE_LOCALE_NUMERIC
USE_LOCALE_TIME
USE_PERLIO
USE_PERL_ATOF
Built under linux
Compiled at Nov 15 2017 19:32:52
@INC:
/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.27.5-387-g006c1a1dbd/da1c/lib/site_perl/5.27.6/x86_64-linux
/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.27.5-387-g006c1a1dbd/da1c/lib/site_perl/5.27.6
/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.27.5-387-g006c1a1dbd/da1c/lib/5.27.6/x86_64-linux
/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.27.5-387-g006c1a1dbd/da1c/lib/5.27.6

--
andreas

p5pRT · 2017-11-23T21:46:57Z

From @cpansprout

On Thu, 23 Nov 2017 13:08:23 -0800, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that DBM::Deep can use, so that it can be fixed permanently. Currently DBM::Deep delves inside warnings.pm internals.

--

Father Chrysostomos

p5pRT · 2017-11-23T21:46:57Z

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

p5pRT · 2018-02-06T01:53:57Z

From @jkeenan

On Thu, 23 Nov 2017 21:46:57 GMT, sprout wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

DBM::Deep once again installs on blead (v5.27.9 (v5.27.8-154-g4bfb553))
--
James E Keenan (jkeenan@cpan.org)

p5pRT · 2018-02-06T01:53:58Z

@jkeenan - Status changed from 'open' to 'pending release'

p5pRT · 2018-02-06T04:33:32Z

From @cpansprout

On Mon, 05 Feb 2018 17:53:57 -0800, jkeenan wrote:

On Thu, 23 Nov 2017 21:46:57 GMT, sprout wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

DBM::Deep once again installs on blead (v5.27.9 (v5.27.8-154-g4bfb553))

Not when I test it. I get the same failure as before.

--

Father Chrysostomos

p5pRT · 2018-02-06T13:53:27Z

@jkeenan - Status changed from 'pending release' to 'open'

p5pRT · 2018-02-06T13:54:41Z

From @jkeenan

On Tue, 06 Feb 2018 04:33:32 GMT, sprout wrote:

On Mon, 05 Feb 2018 17:53:57 -0800, jkeenan wrote:

On Thu, 23 Nov 2017 21:46:57 GMT, sprout wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

DBM::Deep once again installs on blead (v5.27.9 (v5.27.8-154-g4bfb553))

Not when I test it. I get the same failure as before.

So, is this now OS-specific? Mine was Linux (Ubuntu 16.04 LTS) unthreaded.

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

p5pRT · 2018-02-06T19:15:02Z

From @eserte

Dana Tue, 06 Feb 2018 05:54:41 -0800, jkeenan reče:

On Tue, 06 Feb 2018 04:33:32 GMT, sprout wrote:

On Mon, 05 Feb 2018 17:53:57 -0800, jkeenan wrote:

On Thu, 23 Nov 2017 21:46:57 GMT, sprout wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

DBM::Deep once again installs on blead (v5.27.9 (v5.27.8-154-g4bfb553))

Not when I test it. I get the same failure as before.

So, is this now OS-specific? Mine was Linux (Ubuntu 16.04 LTS) unthreaded.

I still see the failure with perl5.27.8-157-gef80cd9, unthreaded, on a Debian/jessie system (not much different from Ubuntu 16.04).

p5pRT · 2018-03-22T02:57:43Z

From @jkeenan

On Tue, 06 Feb 2018 19:15:02 GMT, slaven@rezic.de wrote:

Dana Tue, 06 Feb 2018 05:54:41 -0800, jkeenan reče:

On Tue, 06 Feb 2018 04:33:32 GMT, sprout wrote:

On Mon, 05 Feb 2018 17:53:57 -0800, jkeenan wrote:

On Thu, 23 Nov 2017 21:46:57 GMT, sprout wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-
a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing()
was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255
(wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently.
Currently
DBM::Deep delves inside warnings.pm internals.

DBM::Deep once again installs on blead (v5.27.9 (v5.27.8-154-
g4bfb553))

Not when I test it. I get the same failure as before.

So, is this now OS-specific? Mine was Linux (Ubuntu 16.04 LTS)
unthreaded.

I still see the failure with perl5.27.8-157-gef80cd9, unthreaded, on a
Debian/jessie system (not much different from Ubuntu 16.04).

And in my CPAN-River "top 1000" testing it has been failing month after month. See attachment, which was run on FreeBSD-11.0 after the perl-5.27.10 release.

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

p5pRT · 2018-03-22T02:57:43Z

From @jkeenan

{
author => "RKINYON",
dist => "DBM-Deep",
distname => "DBM-Deep-2.0014",
distversion => 2.0014,
grade => "FAIL",
prereqs => undef,
test_output => [
"Building and testing DBM-Deep-2.0014",
"Building DBM-Deep",
"# Testing DBM::Deep against Perl 5.027009 located at /home/jkeenan/var/ytad/testing/perl-5.27.9/bin/perl",
"t/01_basic.t .................... ok",
"t/02_hash.t ..................... ok",
"t/03_bighash.t .................. skipped: You must set \$ENV{LONG_TESTS} to run the long tests",
"t/04_array.t .................... ok",
"t/05_bigarray.t ................. skipped: You must set \$ENV{LONG_TESTS} to run the long tests",
"t/06_error.t .................... ok",
"t/07_locking.t .................. ok",
"t/08_deephash.t ................. skipped: You must set \$ENV{LONG_TESTS} to run the long tests",
"t/09_deeparray.t ................ skipped: You must set \$ENV{LONG_TESTS} to run the long tests",
"t/10_largekeys.t ................ ok",
"t/11_optimize.t ................. ok",
"t/12_clone.t .................... ok",
"t/13_setpack.t .................. ok",
"t/14_filter.t ................... ok",
"t/15_digest.t ................... ok",
"t/16_circular.t ................. ok",
"t/17_import.t ................... ok",
"t/18_export.t ................... ok",
"t/19_crossref.t ................. ok",
"t/20_tie.t ...................... ok",
"t/21_tie_access.t ............... ok",
"t/22_internal_copy.t ............ ok",
"t/23_misc.t ..................... ok",
"t/24_autobless.t ................ ok",
"t/25_tie_return_value.t ......... ok",
"t/26_scalar_ref.t ............... ok",
"t/27_filehandle.t ............... ok",
"t/28_index_sector.t ............. ok",
"t/29_largedata.t ................ ok",
"t/30_already_tied.t ............. ok",
"t/31_references.t ............... ok",
"t/32_dash_ell.t ................. ok",
"t/33_transactions.t ............. ok",
"t/34_transaction_arrays.t ....... ok",
"t/35_transaction_multiple.t ..... ok",
"t/38_data_sector_size.t ......... ok",
"Assignment of stale reference at t/39_singletons.t line 68.",
"# Tests were run but no plan was declared and done_testing() was not seen.",
"# Looks like your test exited with 255 just after 11.",
"t/39_singletons.t ............... ",
"Dubious, test returned 255 (wstat 65280, 0xff00)",
"All 11 subtests passed ",
"t/40_freespace.t ................ ok",
"t/41_transaction_multilevel.t ... ok",
"t/42_transaction_indexsector.t .. ok",
"t/43_transaction_maximum.t ...... ok",
"t/44_upgrade_db.t ............... skipped: 'FileHandle::Fmode' must be installed to run these tests",
"t/45_references.t ............... ok",
"t/46_blist_reindex.t ............ ok",
"t/47_odd_reference_behaviors.t .. ok",
"t/48_autoexport_after_delete.t .. ok",
"t/50_deletes.t .................. ok",
"t/52_memory_leak.t .............. ok",
"t/53_misc_transactions.t ........ ok",
"t/54_output_punct_vars.t ........ ok",
"t/55_recursion.t ................ ok",
"t/56_unicode.t .................. ok",
"t/57_old_db.t ................... ok",
"t/58_cache.t .................... ok",
"t/96_virtual_functions.t ........ ok",
"t/97_dump_file.t ................ ok",
"t/98_pod.t ...................... ok",
"t/99_pod_coverage.t ............. ok",
"",
"Test Summary Report",
"-------------------",
"t/39_singletons.t (Wstat: 65280 Tests: 11 Failed: 0)",
" Non-zero exit status: 255",
" Parse errors: No plan found in TAP output",
"Files=58, Tests=1559, 9 wallclock secs ( 0.31 usr 0.08 sys + 8.06 cusr 1.25 csys = 9.70 CPU)",
"Result: FAIL",
],
via => "App::cpanminus::reporter 0.17 (1.7043)",
}

p5pRT · 2018-04-19T22:30:26Z

From @iabyn

On Thu, Nov 23, 2017 at 01:46:58PM -0800, Father Chrysostomos via RT wrote:

On Thu, 23 Nov 2017 13:08:23 -0800, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

Since the API's now been done, and since it seems agreed that it's
DBM::Dep that needs fixing, is it ok to close this ticket, or at least
remove from the 5.28 blockers list?

--
You live and learn (although usually you just live).

p5pRT · 2018-04-20T00:50:46Z

From @jkeenan

On 04/19/2018 06:29 PM, Dave Mitchell wrote:

On Thu, Nov 23, 2017 at 01:46:58PM -0800, Father Chrysostomos via RT wrote:

On Thu, 23 Nov 2017 13:08:23 -0800, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

Since the API's now been done, and since it seems agreed that it's
DBM::Dep that needs fixing, is it ok to close this ticket, or at least
remove from the 5.28 blockers list?

My recommendation: remove from 5.28 blockers but leave ticket open.

Perhaps upon 5.28.0 release we should move a ticket like this to
Stalled? (Just a thought.)

jimk

p5pRT · 2018-04-20T01:23:12Z

From @cpansprout

On Thu, 19 Apr 2018 15:30:26 -0700, davem wrote:

On Thu, Nov 23, 2017 at 01:46:58PM -0800, Father Chrysostomos via RT
wrote:

On Thu, 23 Nov 2017 13:08:23 -0800,
andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was
not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed

I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.

Since the API's now been done, and since it seems agreed that it's
DBM::Dep that needs fixing, is it ok to close this ticket, or at least
remove from the 5.28 blockers list?

Yes. The only thing that’s holding it up is that I am not currently able to push to github, and I have not yet had time to figure out why. The patches, written by Slaven, have already been applied to my local copy of the DBM-Deep repository.

--

Father Chrysostomos

p5pRT · 2018-04-20T10:56:21Z

From @xsawyerx

On 04/20/2018 12:29 AM, Dave Mitchell wrote:

On Thu, Nov 23, 2017 at 01:46:58PM -0800, Father Chrysostomos via RT wrote:

On Thu, 23 Nov 2017 13:08:23 -0800, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:

bisect
------
commit 006c1a1 (HEAD,
refs/bisect/bad)
Author: Zefram <zefram@fysh.org>
Date: Wed Nov 15 17:41:29 2017 +0000

fix handling of registered warning categories

diagnostics
-----------
http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079-
a334b34ff3ca

Assignment of stale reference at t/39_singletons.t line 68.
# Tests were run but no plan was declared and done_testing() was not
seen.
# Looks like your test exited with 255 just after 11.
t/39_singletons.t ............... Dubious, test returned 255 (wstat
65280, 0xff00)
All 11 subtests passed
I opened ticket #132468 for the purpose of creating an API that
DBM::Deep can use, so that it can be fixed permanently. Currently
DBM::Deep delves inside warnings.pm internals.
Since the API's now been done, and since it seems agreed that it's
DBM::Dep that needs fixing, is it ok to close this ticket, or at least
remove from the 5.28 blockers list?

Removing from 5.28 blockers list makes sense.

p5pRT · 2018-05-20T21:50:23Z

From @cpansprout

Resolved by the release of SPROUT/DBM-Deep-2.0015.tar.gz

--

Father Chrysostomos

p5pRT · 2018-05-20T21:50:24Z

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

p5pRT closed this as completed May 20, 2018

p5pRT added the Severity Low label Oct 19, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bleadperl v5.27.5-387-g006c1a1dbd breaks RKINYON/DBM-Deep-2.0014.tar.gz #16276

Bleadperl v5.27.5-387-g006c1a1dbd breaks RKINYON/DBM-Deep-2.0014.tar.gz #16276

p5pRT commented Nov 23, 2017

p5pRT commented Nov 23, 2017

p5pRT commented Nov 23, 2017

p5pRT commented Nov 23, 2017

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

p5pRT commented Mar 22, 2018

p5pRT commented Mar 22, 2018

p5pRT commented Apr 19, 2018

p5pRT commented Apr 20, 2018

p5pRT commented Apr 20, 2018

p5pRT commented Apr 20, 2018

p5pRT commented May 20, 2018

p5pRT commented May 20, 2018

Bleadperl v5.27.5-387-g006c1a1dbd breaks RKINYON/DBM-Deep-2.0014.tar.gz #16276

Bleadperl v5.27.5-387-g006c1a1dbd breaks RKINYON/DBM-Deep-2.0014.tar.gz #16276

Comments

p5pRT commented Nov 23, 2017

p5pRT commented Nov 23, 2017

From @andk

p5pRT commented Nov 23, 2017

From @cpansprout

p5pRT commented Nov 23, 2017

p5pRT commented Feb 6, 2018

From @jkeenan

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

From @cpansprout

p5pRT commented Feb 6, 2018

p5pRT commented Feb 6, 2018

From @jkeenan

p5pRT commented Feb 6, 2018

From @eserte

p5pRT commented Mar 22, 2018

From @jkeenan

p5pRT commented Mar 22, 2018

From @jkeenan

p5pRT commented Apr 19, 2018

From @iabyn

p5pRT commented Apr 20, 2018

From @jkeenan

p5pRT commented Apr 20, 2018

From @cpansprout

p5pRT commented Apr 20, 2018

From @xsawyerx

p5pRT commented May 20, 2018

From @cpansprout

p5pRT commented May 20, 2018