-
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
slice.t failures on i386 #469
Comments
http://www.cpantesters.org/cpan/report/26821c66-f085-11ee-80b5-171869899e9e on i686-linux gets similar to yours, but different numbers:
There is another problem that may be connected. https://www.cpantesters.org/cpan/report/43b58a7e-f03b-11ee-be38-1f116e8775ea, on amd64-freebsd, shows:
http://www.cpantesters.org/cpan/report/4c1c59c2-f03b-11ee-be38-1f116e8775ea (on same) shows similar but without the middle failure. |
Do you want to keep supporting 32bit architectures? If not, we'll just remove the packages from those architectures. |
I do want to keep supporting it for the present time. Analysing this particular problem has already revealed a pretty long-standing bug, so I don't want that sort of thing masked! |
I believe that last commit's test captures that this is fixed; it now passes (along with What was going on was that when I added the large negative numbers to get I'll release a new PDL once I've fixed another issue identified: the code to turn an SV into a single value got missed in adding native-complex support, so one can set a complex ndarray's Do you have a capability to test that you agree the immediate issue is fixed, or will that have to wait until I've released the new PDL? |
I could cherry-pick the commits in question and add them as patches to the package, but packaging a new upstream release is easier. If the new release is going to take several days, then adding patches would be quicker. Unfortunately the patches don't apply due to other changes not cherry-picked, so waiting for the new release seems like a better idea than adding a massive patch with all changes since 2.086. |
I've just released 2.087, which I believe fixes the known problems. Please let me know if anything shows up as wrong? |
Confirmed fixed on i386, see: https://salsa.debian.org/perl-team/modules/packages/pdl/-/pipelines/661929 I did have to update the clean target to also remove the generated Makefiles, https://salsa.debian.org/perl-team/modules/packages/pdl/-/pipelines/661944 The package builds on the other 32bit architectures are looking good too: |
Thank you for everything! |
The Debian package build for PDL 2.086 failed to the test failures on i386:
Full buildlog: https://salsa.debian.org/perl-team/modules/packages/pdl/-/jobs/5528286
This issue affects all 32-bit architectures, see:
https://buildd.debian.org/status/package.php?p=pdl
The text was updated successfully, but these errors were encountered: