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 tests on a Win32 Build of Perl 5.18.2 #13674
Comments
From richard.kandarian@lanl.govCreated by richard.kandarian@lanl.govI just built Perl on Win32 using the attached Makefile. The makefile might be peculiar in that USE_IMP_SYS is commented out, PERL_MALLOC not commented out and WIN64 is not commented out. I'm building on a 64 bit Windows 7 Professional system. The build seems to have gone well. I ran nmake /f Makefile.RMK test and got the following result: Test Summary Report The test ../cpan/Module-Build/t/test_file_exts.t hung for a VERY long time, many minutes, so I aborted it and jimmied it to skip itself so that I could get to the rest of the tests. Richard Kandarian Perl Info
|
From @steve-m-hayOn 18 March 2014 13:10, Richard Kandarian <perlbug-followup@perl.org> wrote:
I normally build with USE_IMP_SYS=undef, PERL_MALLOC=define and What compiler are you using? (Is CCTYPE set correctly?)
I have long had a situation where various different tests (often nmake test 2>nul (or to a file instead of the NUL device if you want to see STDERR output). What were the failures with GetShortPathName.t and Unicode.t? Please can you send in the results of ..\perl harness -v ../cpan/Win32/t/GetShortPathName.t (both run from the t/ folder). |
The RT System itself - Status changed from 'new' to 'open' |
From @steve-m-hayOn 18 March 2014 22:45, Steve Hay <steve.m.hay@googlemail.com> wrote:
I've just double-checked that nmake CCTYPE=MSVC100 USE_IMP_SYS=undef PERL_MALLOC=define WIN64=undef passes all tests (with no hangs) for me -- building perl-5.18.2 using |
From richard.kandarian@lanl.govSorry about the lack of attachment. It was my second submission, the first one had the attachment but went to the wrong place since I didn't use perlbug the first time. Also perlbug didn't give me an opportunity to attach anything and I forgot when it left me to send the message myself. It's attached here. I'm using VC++2008 Express. My Windows is also SP1. Richard Kandarian
|
From @steve-m-hayOn 19 March 2014 13:53, Kandarian, Richard M <richard.kandarian@lanl.gov> wrote:
Thanks. I've just tried building 5.18.2 using your makefile, although You didn't send the output from the two tests that failed for you. Are ..\perl harness -v ../cpan/Win32/t/GetShortPathName.t |
From richard.kandarian@lanl.govI did an nmake /f Makefile.RMK clean and then attempted to rebuild Perl in the same directory and it failed. Lots of very perly symbols were missing when attempting to link miniperl.exe. So I moved that directory out of the way and re-extracted the source from the tarball and that problem went away. Then I ran the tests and got the same results so they seem repeatable. There is some more stuff regarding tests after these tests you requested. The tests you requested: C:\cygwin\home\085598\src\perl-5.18.2\t>..\perl harness -v ../cpan/Win32/t/GetShortPathName.t # Expected: "(?^:^\\S{1,8}(\\.\\S{1,3})?$)" ok 3 Test Summary Report ../cpan/Win32/t/GetShortPathName.t (Wstat: 0 Tests: 5 Failed: 1) C:\cygwin\home\085598\src\perl-5.18.2\t>..\perl harness -v ../cpan/Win32/t/Unicode.t not ok 1 # Failed test 3 in t/Unicode.t at line 50 ok 4 ok 6 # t/Unicode.t line 78 is: ok(Win32::GetLongPathName($w32dir), $long); # t/Unicode.t line 86 is: ok(Win32::GetLongPathName($subdir), $long); # Test 11 got: "C:\\cygwin\\home\\085598\\src\\perl-5.18.2\\cpan\\Win32" (t/Unicode.t at line 90) # t/Unicode.t line 90 is: ok(Win32::GetLongPathName(Win32::GetCwd()), $long); Test Summary Report ../cpan/Win32/t/Unicode.t (Wstat: 0 Tests: 11 Failed: 8) These tests don't look good to me at all but I ran tem with ..\perl harness -v and they seem to be successful: io/utf8.t ......................................................... 1/61 # Couldn't unlink 'tmp3432B': Permission denied Richard Kandarian
|
From @steve-m-hayOn 24 March 2014 20:50, Kandarian, Richard M <richard.kandarian@lanl.gov> wrote:
Why is there a 'cygwin' in there? If this is a VC++ build then you What is your PATH set to? Just type "set PATH" in the same Command
That looks like Win32::GetShortPathName() has failed. What does this perl -MWin32 -le "open F, '>Long Path 1908'; print For me it's: LONGPA~1
These all look like Win32::GetANSIPathName() are failing. What does perl -MWin32 -le "$dir=qq[Foo \x{394}\x{419} Bar \x{5E7}\x{645} Baz]; For me it's: FOOBAR~1
This is all quite normal. Some of this noise should certainly be |
From @steve-m-hayI wonder if this is the same problem as #16804? Are you able to confirm whether 8dot3 filename creation is disabled on the drive on which you built perl and ran its tests? |
This comment has been minimized.
This comment has been minimized.
Should this issue be closed? No recent activity and unless the reporter replies to Steve's query, it's not clear what the root cause of the problem was. Currently known test failures due to 8dot3filename support being disabled should be fixed in the next stable perl release via:
|
Migrated from rt.perl.org#121461 (status was 'open')
Searchable as RT121461$
The text was updated successfully, but these errors were encountered: