-
Notifications
You must be signed in to change notification settings - Fork 49
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
SP 5.38.2 fails on GitHub Actions at pl2bat #174
Comments
I cannot reproduce this locally using 5.38.2.2. Which version of 5.38 is being used under CI? Also, what specific flags are you passing to the build? It's possible the issue is related to parallel builds (I ran without any parallel flags). Update: Run from commit: commit bf88db3ec6228c4afb4ef81e1bd1688167728b28 (HEAD -> master, tag: 2.085_02, origin/master, origin/HEAD)
|
The log I excerpted shows 5.38.2. The above was not run from PDL, but PDL-NDBin, so I don't know why you're putting anything about PDL? |
I assumed it was part of the main PDL distro. Will test with PDL-NDBin when I get a chance later today. Can you note the make flags used? e.g. number of parallel runs requested. |
1 similar comment
I assumed it was part of the main PDL distro. Will test with PDL-NDBin when I get a chance later today. Can you note the make flags used? e.g. number of parallel runs requested. |
The CI config is on https://github.com/ebaudrez/PDL-NDBin/blob/master/.github/workflows/ci.yml The action it's using is in PDLPorters/devops, at https://github.com/PDLPorters/devops/blob/master/github-actions/ci-dist/action.yml#L162-L167 which shows the relevant part - it is indeed doing parallel build. I can't see how that would cause a "failure to execute pl2bat"? |
Thanks for the details. The parallel mode might not be relevant, but it's good to be able to eliminate issues, even if unlikely. |
FWIW, it builds fine for me on Windows 11 (with -j8).
instead of as:
|
Thanks Rob. It also builds fine for me on Win11, using both SP 5.38.2.2 and 5.38.0.1. |
If you wanted to have a go at reproducing this in the reported environment, you could fork PDL-NDBin, revert the commit where I version-pinned SP, and then cause the CI to do debugging stuff? |
Just looping back to this. This does not appear to be an issue with Strawberry Perl. So far as I can tell it is either with PDL or ExtUtils::MakeMaker, caused by something like an interaction with MSYS2 paths in a windows shell. The error logs in the first comment are related to a PDL build. The Makefile that errors is under When I build PDL locally and check the generated
All other paths are fully specified. For example L84-L87 contains:
This part of ExtUtils::MakeMaker might be the place to update things: |
I think you're right! Do you mind opening an EUMM issue? This is definitely not something that PDL has any knowing effect on. |
I'll close this issue now. Further discussion is best done on the upstream issue (Perl-Toolchain-Gang/ExtUtils-MakeMaker#459) or PR (Perl-Toolchain-Gang/ExtUtils-MakeMaker#460). |
Excerpt from build of PDL-NDBin just now:
When I switch that CI instead to 5.32, it doesn't have that error.
The text was updated successfully, but these errors were encountered: