ruby_memcheck 1.1.1 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 47dfcdc3712a08c2667460c8889013ed679e23251f445a1ae2a106d8e73d10ad
-  data.tar.gz: 87953c122bb21303ecd219c394fa5ba29b3c6a73c147f64efcc463804ad85b88
+  metadata.gz: 01e474f34ff993ba99b7c554d54bf850c49b8fc8f73fdec8702639373673a088
+  data.tar.gz: a1413639549cc0493adf456b8f38e6dc6463975dab3ef508459809f3b8307031
 SHA512:
-  metadata.gz: 1890f1d919f0c0899be7df94f60875f27618f7e12b99410a0f955fb4722710d37e1efed2d58be00a40ae1d175c585731f95b810ed207075b5aed79e5a834a7d6
-  data.tar.gz: 62b50b839826ee5a65565bbe692fa37aafe16aa5c3de1bd1ae27c85ece57e5ce35b956a0ba7e9e1bf4b7ae40227aa7e1bdf354a2bcbbe77c9231fa6329149ef2
+  metadata.gz: ade6759ab00942eb4dc1ebd5f5e3578d316c49cdf69e979e42ec5d37a8215d139d9765bca26f519158764613d51ed58f01bed055ba70b17860e0d15d7b1c9a89
+  data.tar.gz: 46b92557fbf9dca12a6b3a9f5196d95d54d44b886f06d46beb7b6afe7768476decc921c0f893864e9417328453f45346a4bf91159df8fe3bd529091b19637b90

data/README.md

@@ -121,18 +121,6 @@ The easiest way to use this gem is to use it on your test suite (minitest or RSp
       end
       ```
 
-1. Add the following line to your `test_helper.rb` or `spec_helper.rb`:
-
-    ```ruby
-    at_exit { GC.start }
-    ```
-
-    This will run a major garbage collection cycle before the Ruby process shuts down. This will ensure that any remaining Ruby objects are collected which will prevent Valgrind from reporting false positives.
-
-    It is safest to add the line above at the very first line of `test_helper.rb` or `spec_helper.rb`.
-
-    - **For minitest:** It is important that the line above is added BEFORE the `require "minitest/autorun"` line.
-
 1. You're ready to run your test suite with Valgrind using `rake test:valgrind` or `rake spec:valgrind`! Note that this will take a while to run because Valgrind will make Ruby significantly slower.
 1. (Optional) If you find false positives in the output, you can create Valgrind suppression files. See the [`Suppression files`](#suppression-files) section for more details.
 

data/lib/ruby_memcheck/rspec/rake_task.rb

@@ -40,6 +40,7 @@ module RubyMemcheck
       def spec_command
         # First part of command is Ruby
         args = super.split(" ")[1..]
+        args.unshift("-r" + File.expand_path(File.join(__dir__, "../test_helper.rb")))
 
         configuration.command(args)
       end

data/lib/ruby_memcheck/test_helper.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+at_exit { GC.start }

data/lib/ruby_memcheck/test_task.rb

@@ -18,6 +18,7 @@ module RubyMemcheck
     end
 
     def ruby(*args, **options, &block)
+      args.unshift("-r" + File.expand_path(File.join(__dir__, "test_helper.rb")))
       command = configuration.command(args)
       sh(command, **options) do |ok, res|
         report_valgrind_errors

data/lib/ruby_memcheck/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RubyMemcheck
-  VERSION = "1.1.1"
+  VERSION = "1.2.0"
 end

data/suppressions/ruby.supp

@@ -23,7 +23,6 @@
   recursive_list_access creates a hash called `list` that is stored on the threadptr_recursive_hash. This is reported as a memory leak.
   Memcheck:Leak
   ...
-  fun:rb_st_init_table
   fun:rb_ident_hash_new
   fun:recursive_list_access
   fun:exec_recursive

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby_memcheck
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.2.0
 platform: ruby
 authors:
 - Peter Zhu
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2022-10-19 00:00:00.000000000 Z
+date: 2022-10-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri
@@ -143,6 +143,7 @@ files:
 - lib/ruby_memcheck/rspec/rake_task.rb
 - lib/ruby_memcheck/stack.rb
 - lib/ruby_memcheck/suppression.rb
+- lib/ruby_memcheck/test_helper.rb
 - lib/ruby_memcheck/test_task.rb
 - lib/ruby_memcheck/test_task_reporter.rb
 - lib/ruby_memcheck/valgrind_error.rb