Bug #132080 for Devel-CompileLevel: Test suite fails with perl 5.30.2 RC1

Sat Mar 07 11:10:08 2020 SREZIC [...] cpan.org - Ticket created

Subject:

Test suite fails with perl 5.30.2 RC1

See http://www.cpantesters.org/cpan/report/728c7140-5e82-11ea-b1b5-88ed4f0ee1dc for a sample fail report.

Sat Mar 07 12:09:20 2020 ANDK [...] cpan.org - Correspondence added

Bisect points at: commit b7b8b099a2106c45a577e9cd7b9f1653736cf89a Author: David Mitchell <davem@iabyn.com> Date: Fri Dec 13 13:48:25 2019 +0000 avoid identical stack traces GH #15109 The output of caller() (e.g. as produced by carp::Confess) produces multiple identical outputs when within a nested use/require. This is because at the time of calling the 'BEGIN { require ... }', PL_curcop is set to &PL_compiling, which is a fixed buffer within the interpreter, whose individual file and line fields are saved and restored when doing a new require/eval. This means that within the innermost require, PL_compiling has file:lineno of the innermost source file, and multiple saved PL_curcop values in the context stack frames all point to the same &PL_copmpiling. So all levels of the stack trace appear to come from the innermost file. This commit fixes this (after a fashion) by, at the start of calling a BEGIN, making PL_curcop point to a temporary copy of PL_compiling instead. This is all a bit of a hack. (cherry picked from commit f2f32cd638746f538da6db804dab6dd54e654f30)

Sat Mar 07 12:09:20 2020 The RT System itself - Status changed from 'new' to 'open'

Sat Mar 07 12:13:48 2020 ANDK [...] cpan.org - Correspondence added

RT-Send-CC:

shay [...] cpan.org, DAPM [...] cpan.org

CC'ing Steve and Dave

Mon Mar 09 05:09:20 2020 shay [...] cpan.org - Correspondence added

On Sat Mar 07 12:13:48 2020, ANDK wrote: Show quoted text

> CC'ing Steve and Dave

Thanks for the heads-up, Andreas. I believe this requires a change to Devel-CompileLevel to account for the backporting of the commit that you have bisected to. That commit went into 5.31.7. Devel-CompileLevel was changed in v0.001003 to behave differently for perls > 5.31.6: It no longer goes into the "if (_WARNING_BITS_CHECK)" branch of compile_level() in that case. I think that version check will need changing to account for this perl commit having been backported to 5.30.2 now.