-
Notifications
You must be signed in to change notification settings - Fork 50
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
Failed test 186 - ENV store downgrades utf8 in setenv at op/magic.t line 75 (also test 187) #60
Comments
Would you mind committing your 5.36 setup of spbuild to the repo so we can more accurately test exactly the same way as you are? |
The config files are on the wip_536 branch. I've just pushed the latest changes to skip tests for several CPAN packages. I have uploaded the extlibs to a dev release on https://github.com/StrawberryPerl/build-extlibs/releases/tag/dev_gcc10.3_20230313 I will update the config to point to those files but in the interim the contents of the extlibs_gcc10_20230313.tar file can be extracted to /z/extlibs/_out The build itself is called using Also, if you have a link for how to set up github authentication on the docker instance then please point me to it. At the moment git hangs on push so I'm having to copy the repos to a local machine to push. I assume there is a credential manager command somewhere under powershell but the ones I have found seem to not work as git still hangs on push. |
The builds also need the winlibs distro. I've uploaded that to https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/dev_20230311/winlibs_10.3.zip It is the winlibs 10.3 GCC mingw64 distribution but without mingw being the top level dir so it matches the strawberry expectations, and with |
No idea how to make the oauth authentication work inside docker, but I imagine putting an ssh key in |
These tests pass when building on a local machine instead of under docker. |
Raising a separate issue so as not to clutter #56
From #56 (comment)
These failures are appearing in the perl tests when running under GCC 10.
The only other case I can find is from 2013 and it was unresolved: https://www.nntp.perl.org/group/perl.perl5.porters/2013/05/msg201832.html
Possibly it is an artefact of running under docker. Or it is related to the compiler (I have not checked with GCC 11). Maybe it is a codepage setting somewhere?
The text was updated successfully, but these errors were encountered: