Dir.chdir raises a SystemCallError if the original directory no longer exists
-----------------------------------------------------------------------------

                 Key: JRUBY-2017
                 URL: http://jira.codehaus.org/browse/JRUBY-2017
             Project: JRuby
          Issue Type: Bug
          Components: Core Classes/Modules
    Affects Versions: JRuby 1.1RC1
         Environment: Ubuntu 7.10
            Reporter: Wirianto Djunaidi
         Attachments: dir_chdir.patch

Current Dir.chdir failed rubinius spec for nested Dir.chdir where the inner 
nested Dir delete the upper nested Dir.
When investigating the issue I found out that RubyDir.getDir() logic is not 
really testing if the Directory that must exist
does exist so I added that in also.

Started
......F.

1)
Dir.chdir raises a SystemCallError if the original directory no longer exists 
FAILED
Expected SystemCallError but no exception was raised: 
./mspec/expectations.rb:10:in `fail_with'
./mspec/expectations/should.rb:6:in `should'
/home/shared/rubinius/./spec/ruby/1.8/core/dir/chdir_spec.rb:51
/home/shared/rubinius/./spec/ruby/1.8/core/dir/chdir_spec.rb:51:in `call'
./mspec/runner/runner.rb:136:in `describe'
./mspec/runner/runner.rb:135:in `each'
./mspec/runner/runner.rb:130:in `describe'
./mspec/runner/runner.rb:135:in `describe'
/home/shared/rubinius/./spec/ruby/1.8/core/dir/chdir_spec.rb:4
/home/shared/rubinius/./spec/ruby/1.8/core/dir/chdir_spec.rb:4:in `load'
tmp/last_mspec.rb:15
tmp/last_mspec.rb:10:in `each'
tmp/last_mspec.rb:10

Finished in 0.451000 seconds

8 examples, 12 expectations, 1 failure, 0 errors


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to