Skip to content
This repository was archived by the owner on Nov 30, 2024. It is now read-only.

Disable memory leak spec for TruffleRuby #2685

Merged

Conversation

bjfish
Copy link
Contributor

@bjfish bjfish commented Jan 9, 2020

GC.disable and GC.enable are mock implementations in TruffleRuby which causes this spec to fail.

@JonRowe JonRowe merged commit 7c2531e into rspec:master Jan 9, 2020
@bjfish bjfish deleted the disable-memory-leak-spec-for-truffleruby branch January 9, 2020 16:38
@JonRowe
Copy link
Member

JonRowe commented Jan 9, 2020

In future we might do something about this in rspec-support for improving the detection of Rubies supporting such tweaks but for now I see no harm in merging this.

@JonRowe
Copy link
Member

JonRowe commented Jan 9, 2020

Thanks!

@eregon
Copy link
Contributor

eregon commented Jan 9, 2020

A conservative check for this would be to only try GC.enable/GC.disable if RUBY_ENGINE == 'ruby'.
Most VMs don't allow to disable GC dynamically because it's so dangerous.

@benoittgt
Copy link
Member

Thanks for all of those patch for TruffleRuby

MatheusRich pushed a commit to MatheusRich/rspec-core that referenced this pull request Oct 30, 2020
…r-truffleruby

Disable memory leak spec for TruffleRuby
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants