-
Notifications
You must be signed in to change notification settings - Fork 46
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
t/inlinepdlpp.t fails for Strawberry Perl 5.38.0 #442
Comments
The build passes when |
...although it still fails when it is built under the Strawberry Perl build system, so it could be related to that and thus a false negative related to the build path. |
Could you say here which version of Inline is installed there? It seems (given the code in that test file is fairly simple and works very widely) like it might be a bug in Inline. |
Also, it would be very helpful to uncomment the |
It's a fresh build so uses the latest Inline.
I'll report more when I've had a chance to try this. |
Could you report any further findings, or close this if it has gone away? |
It would seem likely to be an issue with the length of the path. A similar issue was noted for Inline::C in StrawberryPerl/Perl-Dist-Strawberry#95 It does not affect most Strawberry Perl users since the build path is short by default. However, under the SP build system it is built under a deeper path. |
Is this an Inline problem, rather than a PDL one? If so, could an issue be opened there, and closed here? |
All the indications are that the problem manifests with Inline. It has been report at ingydotnet/inline-c-pm#103 I'll close this one. |
Excerpts from the build log below (test failures then start of log). Please let me know if you want the full log or other subsets.
This might also affect other versions of Strawberry Perl but has not appeared in previous testing.
Oddly, the install goes ahead.(Edit: The Strawberry Perl config is currently to ignore test failures, a left over from earlier times).This could be a parallelisation issue. The previous builds did not use this. I'll post an update when a non-parallel build is complete.
Env vars:
Test failure:
Start of build:
The text was updated successfully, but these errors were encountered: