phasis at gmail.com
Wed Nov 20 15:22:01 UTC 2013
2013/11/20 Daniel Berger <djberg96 at gmail.com>:
> On Wed, Nov 20, 2013 at 7:31 AM, Daniel Berger <djberg96 at gmail.com> wrote:
>>> > You shouldn't be getting the "rake aborted!" though. If you fix that
>>> > test
>>> > and run them again do you still see that?
>>> It seems that "rake aborted!" means there is at least one failure.
>>> I'm not sure it is a bug of feature, a simple test with
>>> "assert_equal(1,2)" produce "rake aborted!"
>> I'm seeing it every other run, even without test failures:
>> C:\Users\djberge\Repositories\win32-file>rake test:link
>> c:/ruby264/bin/ruby.exe -w -I"lib"
>> warning: method redefined; discarding old initialize
>> Loaded suite
>> Finished in 0.128007 seconds.
>> 17 tests, 26 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0
>> notifications 100% passed
>> 132.81 tests/s, 203.11 assertions/s
>> rake aborted!
>> Command failed with status (116): [ruby -w -I"lib"
>> "test/test_win32_file_link.rb" ]
>> Tasks: TOP => test:link
>> (See full trace by running task with --trace)
> BTW, I'm seeing this with the latest in FFI, which fixes one test, and makes
> the File.readlink method raise an error if the argument is not a symlink.
OK, I can reproduce rake test segfaults with the latest FFI and ruby
I fixed the code and committed.
BTW, I think the wstrip method should be changed.
Currently, It ignores encoding and cannot handles multibyte character
code like CP949.
More information about the win32utils-devel