1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Show what objects were actually allocated on allocation count tests

Browse Source 
According to Launchable, these tests fail randomly

```
Failure:
TestStringMemory#test_byteslice_prefix [D:/a/ruby/ruby/src/test/ruby/test_string_memory.rb:33]:
<1> expected but was
<2>.
```

https://app.launchableinc.com/organizations/ruby/workspaces/ruby/data/test-paths/file%3Dtest%2Fruby%2Ftest_string_memory.rb%23%23%23class%3DTestStringMemory%23%23%23testcase%3Dtest_byteslice_prefix?testSessionStatus=flake
This commit is contained in:
Yusuke Endoh 2024-08-02 21:44:43 +09:00
parent 303d2319f0
commit 3f93ef06a8
Notes: git 2024-08-02 14:29:56 +00:00 
Merged: https://github.com/ruby/ruby/pull/11295
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
test/ruby/test_string_memory.rb
View File

@ -30,7 +30,7 @@ class TestStringMemory < Test::Unit::TestCase
string.byteslice(0, 50_000)
end
assert_equal 1, allocations.size
assert_equal 1, allocations.size, "One object allocation is expected, but allocated: #{ allocations.inspect }"
end
def test_byteslice_postfix
@ -40,7 +40,7 @@ class TestStringMemory < Test::Unit::TestCase
string.byteslice(50_000, 100_000)
end
assert_equal 1, allocations.size
assert_equal 1, allocations.size, "One object allocation is expected, but allocated: #{ allocations.inspect }"
end
def test_byteslice_postfix_twice
@ -50,6 +50,6 @@ class TestStringMemory < Test::Unit::TestCase
string.byteslice(50_000, 100_000).byteslice(25_000, 50_000)
end
assert_equal 2, allocations.size
assert_equal 2, allocations.size, "Two object allocations are expected, but allocated: #{ allocations.inspect }"
end
end