Mercurial > hgsubversion
view tests/test_helpers.py @ 1539:0ebcc5bbf692
tests: when making a `memctx`, make sure to use a single repo instance
The way self.repo is dynamic produces bad lock behavior because the
`context.memctx` ends up with a different instance than self in
`localrepo.commitctx`, which means the callbacks in the `memctx` get
an unlocked repo instance. This causes lock warning failures. When
it's not a code freeze for core, we should probably:
* Make lock failures hard, not just warnings
* Stop holding a repo reference in memctx, or otherwise check it's the same
instance as `self` during `localrepo.commitctx`
That's my best guess based on the (very hard to debug) test failures here.
author | Augie Fackler <raf@durin42.com> |
---|---|
date | Sat, 28 Oct 2017 21:34:52 -0400 |
parents | 8d8fc10d0d0a |
children |
line wrap: on
line source
import os, sys, unittest _rootdir = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) sys.path.insert(0, _rootdir) from hgsubversion import editor class TestHelpers(unittest.TestCase): def test_filestore(self): fs = editor.FileStore(2) fs.setfile('a', 'a') fs.setfile('b', 'b') self.assertEqual('a', fs._data.get('a')) self.assertEqual('b', fs._data.get('b')) fs.delfile('b') self.assertRaises(IOError, lambda: fs.getfile('b')) fs.setfile('bb', 'bb') self.assertTrue('bb' in fs._files) self.assertTrue('bb' not in fs._data) self.assertEqual('bb', fs.getfile('bb')) fs.delfile('bb') self.assertTrue('bb' not in fs._files) self.assertEqual([], os.listdir(fs._tempdir)) self.assertRaises(IOError, lambda: fs.getfile('bb')) fs.setfile('bb', 'bb') self.assertEqual(1, len(os.listdir(fs._tempdir))) fs.popfile('bb') self.assertEqual([], os.listdir(fs._tempdir)) self.assertRaises(editor.EditingError, lambda: fs.getfile('bb')) fs.close()