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
Odd sharing of files between forked processes #2430
Comments
I've updated the issue with different paths to call rbx, since I was totally confused at first that this worked fine, but it was invoking MRI on my system, since |
Ok, this seems to have nothing to do with forking, but with a problem with our compiled code caching. If I do the following, it works correctly for me:
This basically disables caching compiled Ruby code. For some reason it doesn't see |
Perfect, thanks for isolating it further. The bug manifested itself in some of my code that forked, so it's the example I was able to isolate. What does Rubinius use to determine if code needs to be recompiled? Maybe it's related to timing if it's using something like file mtime. |
rubinius/rubinius#2430 is resolved
rubinius/rubinius#2430 is resolved --- This commit was imported from rspec/rspec-core@be91a59.
Consider:
first!second!
is expected.Also reproducable with
RBXOPT=-X19
The text was updated successfully, but these errors were encountered: