sapling/tests/test-hgsubversion-fetch-exec.py
Jun Wu 9dc21f8d0b codemod: import from the edenscm package
Summary:
D13853115 adds `edenscm/` to `sys.path` and code still uses `import mercurial`.
That has nasty problems if both `import mercurial` and
`import edenscm.mercurial` are used, because Python would think `mercurial.foo`
and `edenscm.mercurial.foo` are different modules so code like
`try: ... except mercurial.error.Foo: ...`, or `isinstance(x, mercurial.foo.Bar)`
would fail to handle the `edenscm.mercurial` version. There are also some
module-level states (ex. `extensions._extensions`) that would cause trouble if
they have multiple versions in a single process.

Change imports to use the `edenscm` so ideally the `mercurial` is no longer
imported at all. Add checks in extensions.py to catch unexpected extensions
importing modules from the old (wrong) locations when running tests.

Reviewed By: phillco

Differential Revision: D13868981

fbshipit-source-id: f4e2513766957fd81d85407994f7521a08e4de48
2019-01-29 17:25:32 -08:00

33 lines
1.1 KiB
Python

# no-check-code -- see T24862348
import test_hgsubversion_util
from edenscm.mercurial import node
class TestFetchExec(test_hgsubversion_util.TestBase):
stupid_mode_tests = True
def assertexec(self, ctx, files, isexec=True):
for f in files:
self.assertEqual(isexec, "x" in ctx[f].flags())
def test_exec(self):
repo = self._load_fixture_and_fetch("executebit.svndump")
self.assertexec(repo[0], ["text1", "binary1", "empty1"], True)
self.assertexec(repo[0], ["text2", "binary2", "empty2"], False)
self.assertexec(repo[1], ["text1", "binary1", "empty1"], False)
self.assertexec(repo[1], ["text2", "binary2", "empty2"], True)
def test_empty_prop_val_executable(self):
repo = self._load_fixture_and_fetch("executable_file_empty_prop.svndump")
self.assertEqual(
node.hex(repo["tip"].node()), "08e6b380bf291b361a418203a1cb9427213cd1fd"
)
self.assertEqual(repo["tip"]["foo"].flags(), "x")
if __name__ == "__main__":
import silenttestrunner
silenttestrunner.main(__name__)