tahoe-lafs/tahoe-lafs
tahoe-lafs
/
tahoe-lafs
2
0
Fork 0
Code Issues Pull Requests 23 Packages Projects Releases 1 Wiki Activity

relying on memory/gc bad

This commit is contained in:
meejah 2019-12-07 03:20:01 -07:00
parent ca5e1ebe52
commit a348d3d507
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/allmydata/test/test_storage.py
View File

@ -1,4 +1,5 @@
import time, os.path, platform, stat, re, json, struct, shutil import time, os.path, platform, stat, re, json, struct, shutil
import gc
from twisted.trial import unittest from twisted.trial import unittest
@ -553,8 +554,14 @@ class Server(unittest.TestCase):
# we abandon the first set, so their provisional allocation should be # we abandon the first set, so their provisional allocation should be
# returned # returned
# XXX okay, so the weak-key-dictionary in storage-server is
# basically making an interface to the storage-server that is
# "whenever I drop my object AND the garbage-collector removes
# it, *then* that thing is no longer writing"..? ... yuuuuck.
del already del already
del writers del writers
gc.collect() # for pypy's benefit
self.failUnlessEqual(len(ss._active_writers), 1) self.failUnlessEqual(len(ss._active_writers), 1)
# now we have a provisional allocation of 1001 bytes # now we have a provisional allocation of 1001 bytes
@ -567,6 +574,7 @@ class Server(unittest.TestCase):
del already2 del already2
del writers2 del writers2
del bw del bw
gc.collect() # for pypy's benefit
self.failUnlessEqual(len(ss._active_writers), 0) self.failUnlessEqual(len(ss._active_writers), 0)
# this also changes the amount reported as available by call_get_disk_stats # this also changes the amount reported as available by call_get_disk_stats