-
Notifications
You must be signed in to change notification settings - Fork 1
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\spec\S32-io\io-spec-win.t fails on Windows 10 with MSVS 2013 #4846
Comments
From @nanisHello: Just built using http://rakudo.org/downloads/star/rakudo-star-2015.11.tar.gz. During `nmake rakudo-spectest`, I noticed a number of test failures. ok 206 - updir is ".." # Looks like you planned 209 tests, but ran 206 Test Summary Report t\spec\S32-io\io-spec-win.t (Wstat: 65280 Tests: 206 Failed: 0) And, here is the relevant section in the test file: if $*DISTRO.name !~~ any(<mswin32 netware symbian os2 dos>) { It seems somehow IO::Spec is not delegating properly, but I haven't C:\> perl6 -e "say IO::Spec::Win32.devnull" C:\> perl6 -e "say IO::Spec.devnull" C:\> perl6 -e "say IO::Spec" C:\> perl6 -e "say IO::Spec::Win32" And, for sanity: C:\> perl6 -e "use nqp; say I am afraid I do not know where to go from here, but FYI. HTH, -- Sinan |
From @nanis
Pull request submitted. I hope this is the right place to do that: The fix I propose is to invoke methods on $*SPEC rather than IO::Spec. HTH, -- Sinan |
1 similar comment
From @nanis
Pull request submitted. I hope this is the right place to do that: The fix I propose is to invoke methods on $*SPEC rather than IO::Spec. HTH, -- Sinan |
From @labster
I approved the pull request. If the tests pass on Windows, this ticket can be resolved. |
The RT System itself - Status changed from 'new' to 'open' |
From @labsterOn Mon Dec 14 09:29:37 2015, labster wrote:
Given the complete lack of activity/complaints in 4 months, I'm going to assume that the tests pass on Windows. Resolving ticket. |
@labster - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126876 (status was 'resolved')
Searchable as RT126876$
The text was updated successfully, but these errors were encountered: