Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for Perl 5.37.9 but no version bump. (Deal with eval exception text change) #6

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

demerphq
Copy link

Fixes the 5.37.9 test failure, silences "not imported" warnings during test.

The test failure is related to: Perl/perl5#20357

Fixes: Perl/perl5#20864

This is the same as #5 but does not include any version bump or changes to the Makefile.PL

…rors

In Perl/perl5#20357 the Perl dev team fixed some
inconsistencies in how eval behaved with regard to compile errors. Prior
that PR the exact outcome of a compile error varied with the type and
number of errors that were encountered, sometimes calling $SIG{__DIE__},
sometimes not, sometimes outputing "Execution ... aborted" messages,
sometimes not. With the merge of that PR the behavior is now consistent,
and in particular for this module the "Execution ... aborted" message is
now always output when there is a compile error.

This patch strips this message off the error before rethrowing the
exception with _croak().

This patch also includes some minor changes to the code to make it
easier to debug the code being eval()ed which I left commented out. I
figured if it was useful to debug this issue then it might useful again
in the future.
…stinct var names

Using "$FILE" in multiple tests causes the "not imported" warnings.
Simply replacing them with distinct names causes the warnings to go away.
@demerphq demerphq force-pushed the yves/fix_for_perl_5_37_9_no_version_bump branch from 61bca8e to eff95bd Compare April 16, 2023 12:40
eserte added a commit that referenced this pull request Jul 8, 2023
@eserte
Copy link
Owner

eserte commented Jul 8, 2023

Hi @demerphq, thanks for the PR. I will review it later, however, for a quick fix I will just do a release where the problematic test case is just marked as TODO (5.37.9 and later).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants