refining valgrind suppressions for ruby 2.6

because a few more false positives came out. URLs of the failing builds is preserved in the file.
sparklemotion · Mar 6, 2019 · 9224158 · 9224158
1 parent 2340bd7
commit 9224158
Showing 1 changed file with 7 additions and 6 deletions.
diff --git a/suppressions/nokogiri_ruby-2.6.supp b/suppressions/nokogiri_ruby-2.6.supp
@@ -1,18 +1,17 @@
 {
-   <https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-2.6-valgrind/builds/1>
+   https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-2.6-valgrind/builds/1,https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri-pr/jobs/ruby-2.6-valgrind/builds/11
    Memcheck:Addr8
    fun:mark_locations_array
    fun:gc_marks_wb_unprotected_objects
    fun:gc_marks_finish
-   fun:gc_marks_rest
    ...
    fun:ruby_finalize_?
    fun:ruby_cleanup
    fun:ruby_run_node
    fun:main
 }
 {
-   <https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-2.6-valgrind/builds/1>
+   https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-2.6-valgrind/builds/1
    Memcheck:Addr8
    fun:mark_locations_array
    fun:gc_mark_stacked_objects
@@ -25,13 +24,15 @@
    fun:main
 }
 {
-   <https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-libxmlruby-valgrind/builds/116>
+   https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri/jobs/ruby-libxmlruby-valgrind/builds/116,https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri-pr/jobs/ruby-libxmlruby-valgrind/builds/13
    Memcheck:Addr8
    fun:mark_locations_array
    fun:gc_mark_stacked_objects
    fun:gc_mark_stacked_objects_all
    fun:gc_marks_rest
    ...
-   fun:garbage_collect_with_gvl
-   ...
+   fun:ruby_finalize_?
+   fun:ruby_cleanup
+   fun:ruby_run_node
+   fun:main
 }