-
Notifications
You must be signed in to change notification settings - Fork 553
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
5.36.2a t/porting/regen.t blows up under macOS: undefined current object: op.o #21677
Comments
|
Frankly, libperl.t is so fragile we should consider eliminating it entirely. |
|
I haven't exercised 5.36.2a extensively, but I do know I have found nothing wrong with 5.38.1 built on the same system other than the test failure that 5.38.1a was supposed to fix. Please let me know what other information I can provide. My XCode is 14.3.1. |
|
Same result with https://www.leonerd.org.uk/tmp/perl-5.36.3.tar.gz t/porting/libperl ................................................ porting/libperl.t: undefined current object: op.o: at porting/libperl.t line 242, <$nm_fh> line 2. |
|
Have not used 5.36.3 a lot, but installed all my usual modules without problems. I assume the error is cosmetic. |
|
This was fixed for 5.38 in b1db177 and hasn't been backported to You can ignore the message. I expect we should be disabling this test for maint, or at least when run outside of perl's |
maint-* branches, whether supported or not, may not be updated to handle changes to nm's output due to updates to the operating system or toolchain. The same applies doubly to release tarballs. So skip this test for maint/version numbers. Keep the test for devel releases, since they have limited support windows anyway, and we want this test to be done where possible. Fixes Perl#21677
maint-* branches, whether supported or not, may not be updated to handle changes to nm's output due to updates to the operating system or toolchain. The same applies doubly to release tarballs. So skip this test for maint/version numbers. Keep the test for devel releases, since they have limited support windows anyway, and we want this test to be done where possible. Fixes Perl#21677
maint-* branches, whether supported or not, may not be updated to handle changes to nm's output due to updates to the operating system or toolchain. The same applies doubly to release tarballs. So skip this test for maint/version numbers. Keep the test for devel releases, since they have limited support windows anyway, and we want this test to be done where possible. Fixes #21677
Module:
Description
When running the Perl test suite, t/porting/regen.t failed as follows:
t/porting/libperl ................................................ porting/libperl.t: undefined current object: op.o: at porting/libperl.t line 242, <$nm_fh> line 2.
FAILED--no leader found
./perl harness added nothing that appears interesting, at least not that I can tell.
porting/libperl.t: undefined current object: op.o: at porting/libperl.t line 242, <$nm_fh> line 2.
porting/libperl.t ....................................................
Dubious, test returned 29 (wstat 7424, 0x1d00)
No subtests run
./perl -I. -MTestInit t/porting/regen.t (stolen from #21671) ran to completion with no failing tests, but I don't know what that means.
Steps to Reproduce
Sorry, it's more than just a one-liner:
Expected behavior
Passing test
Perl configuration
The text was updated successfully, but these errors were encountered: