-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
"str".freeze optimization sporadically produces a different object #5070
Milestone
Comments
headius
added a commit
that referenced
this issue
Mar 1, 2018
I think this was due to the entire rubyspec suite running with |
FYI |
headius
added a commit
that referenced
this issue
Aug 1, 2019
This was likely failing because we ran the full RubySpec suite with --debug when run through rake. This turned on frozen string debugging, which disabled the deduplication this spec tests. Fixes #5070.
Adithya-copart
pushed a commit
to Adithya-copart/jruby
that referenced
this issue
Aug 25, 2019
This was likely failing because we ran the full RubySpec suite with --debug when run through rake. This turned on frozen string debugging, which disabled the deduplication this spec tests. Fixes jruby#5070.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a newly-modified spec that tests
"abc".freeze.equal?("abc".freeze)
and it appears to be intermittently failing. It appears to fail consistently on Travis.[The spec] looks like this:
And fails like this:
See #4970 for a related issue we believed we fixed in 9.1.16.
The text was updated successfully, but these errors were encountered: