[ruby-core:66956] [ruby-trunk - Bug #10618] TestWeakRef#test_repeated_object_leak fails on ARM

Issue #10618 has been updated by Eric Wong.


 Is 60 seconds enough?  Can 30 work?  Default is only 10 seconds.
 
 diff --git a/test/test_weakref.rb b/test/test_weakref.rb
 index 36b5d5b..d21b431 100644
 --- a/test/test_weakref.rb
 +++ b/test/test_weakref.rb
 @@ -63,7 +63,7 @@ class TestWeakRef < Test::Unit::TestCase
  
    def test_repeated_object_leak
      bug10537 = '[ruby-core:66428]'
 -    assert_no_memory_leak(%w(-rweakref), '', <<-'end;', bug10537)
 +    assert_no_memory_leak(%w(-rweakref), '', <<-'end;', bug10537, timeout: 60)
        a = Object.new
        150_000.times { WeakRef.new(a) }
      end;

----------------------------------------
Bug #10618: TestWeakRef#test_repeated_object_leak fails on ARM
https://bugs.ruby-lang.org/issues/10618#change-50497

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Eric Wong
* Category: 
* Target version: 
* ruby -v: ruby -v: ruby 2.2.0dev (2014-12-17 trunk 48879) [armv7hl-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
I observer following error on Fedora's ARM builders:

~~~
  1) Error:
TestWeakRef#test_repeated_object_leak:
Timeout::Error: execution of assert_no_memory_leak expired
    /builddir/build/BUILD/ruby-2.2.0-r48879/test/test_weakref.rb:66:in `test_repeated_object_leak'
~~~

This issue was very likely introduced by r48820. Less iterations or longer timeout might help probably.



-- 
https://bugs.ruby-lang.org/