Issue #5135 has been updated by Motohiro KOSAKI.


And, below is rest comments.

> 28) Failure:
> test_noctty(TestIO_Console) [/builddir/build/BUILD/ruby-1.9.3-preview1/test/io/console/test_io_console.rb:183]:
> <["nil"]> expected but was
> <["#<File:/dev/tty>"]>.

Please confirm two points. 1) does your system have /dev/tty? 2) Does your SELinux policy disallow to access it?



> 29) Failure:
> test_jobs_status(TestParallel::TestParallel) [/builddir/build/BUILD/ruby-1.9.3-preview1/test/testunit/test_parallel.rb:174]:
>  30) Failure:
> test_no_retry_option(TestParallel::TestParallel) [/builddir/build/BUILD/ruby-1.9.3-preview1/test/testunit/test_parallel.rb:168]:
>  31) Failure:
> test_should_retry_failed_on_workers(TestParallel::TestParallel) [/builddir/build/BUILD/ruby-1.9.3- 32) Failure:
>  32) Failure:
> test_should_run_all_without_any_leaks(TestParallel::TestParallel) [/builddir/build/BUILD/ruby-1.9.3->
>  preview1/test/testunit/test_parallel.rb:155]:

This four failure has already been fixed. see  [Bug #5132]


> DB->del: attempt to modify a read-only database

This is DB4 false positive warnings. Our test case intentionally try to modiry read-only database and check error code.
And DB4 makes annoying warnings everytimes. We don't have any idea to fix it.

Because of, ext/dbm support following dbm families.
    db, db1, db2, db3, db4, db5, dbm, gdbm, qdbm, 

Therefore we can only use common api sets in them. IOW, db4 specific hack is hard to be merged.
Do you have any idea?


----------------------------------------
Bug #5135: Ruby 1.9.3-preview1 tests fails in Fedora Rawhide
http://redmine.ruby-lang.org/issues/5135

Author: Vit Ondruch
Status: Feedback
Priority: Normal
Assignee: Motohiro KOSAKI
Category: 
Target version: 1.9.3
ruby -v: -


It would be nice if all test are green before release.

https://gist.github.com/1118196


-- 
http://redmine.ruby-lang.org