This project is archived and is in readonly mode.
test_atomic_write_preserves_default_file_permissions(AtomicWriteTest) fails when umask is not 0022
Reported by S. Brent Faulkner | August 13th, 2008 @ 11:13 PM | in 2.x
When running tests with a umask other than 0022 the test_atomic_write_preserves_default_file_permissions(AtomicWriteTest) test will fail with:
1) Failure: test_atomic_write_preserves_default_file_permissions(AtomicWriteTest)
[./test/core_ext/file_test.rb:53:in `test_atomic_write_preserves_default_file_permissions'
./test/../lib/active_support/testing/setup_and_teardown.rb:94:in `__send__'
./test/../lib/active_support/testing/setup_and_teardown.rb:94:in `run']:
<"100644"> expected but was <"100664">.
Comments and changes to this ticket
-
S. Brent Faulkner August 13th, 2008 @ 11:14 PM
I have a fix for the test, but as this is my first attempt at submitting a patch have not yet progressed quite that far... stay tuned (unless you fix the test first).
-
S. Brent Faulkner August 14th, 2008 @ 12:28 AM
- no changes were found...
-
S. Brent Faulkner August 14th, 2008 @ 12:28 AM
- Tag changed from “bug” to “bug, patch”
To reproduce the problem set your umask to 0002...
$ umask 0002
Then run your tests...
$ rake test
I've attached a patch to fix it.
-
josh August 14th, 2008 @ 03:00 AM
- State changed from “new” to “resolved”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
josh
S. Brent Faulkner