Source: libparse-errorstring-perl-perl
Version: 0.21-1
Severity: important
User: [email protected]
Usertags: perl-5.22-transition
Tags: sid stretch upstream patch
Forwarded: https://github.com/PadreIDE/Parse-ErrorString-Perl/issues/1

This package FTBFS with perl 5.22 (currently in experimental):

#   Failed test 'diagnostics'
#   at t/04-perldiag.t line 64.
# +---+-------+---+-------------------------------------------------------------
----------------+
# | Ln|Got    | Ln|Expected                                                     
                |
# +---+-------+---+-------------------------------------------------------------
----------------+
# *  1|undef  *  1|'(F) You\'ve said "use strict" or "use strict vars", which in
dicates         *
# |   |       *  2|that all variables must either be lexically scoped (using "my
" or "state"),  *
# |   |       *  3|declared beforehand using "our", or explicitly qualified to s
ay              *
# |   |       *  4|which package the global variable is in (using "::").'       
                *
# +---+-------+---+-------------------------------------------------------------
----------------+

#   Failed test 'type'
#   at t/04-perldiag.t line 65.
#          got: undef
#     expected: 'F'

#   Failed test 'error type'
#   at t/04-perldiag.t line 66.
#          got: undef
#     expected: 'fatal error'
# Looks like you failed 3 tests of 4.
t/04-perldiag.t ........... 
1..4
ok 1 - message
not ok 2 - diagnostics
not ok 3 - type
not ok 4 - error type
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/4 subtests 
t/05-stacktrace.t ......... 

There is a patch on the GH issue.

This bug will become release critical nearer the time of the perl 5.22
migration, expected during the (northern hemisphere) summer.

Cheers,
Dominic.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to