sapling/tests/test-hgsubversion-fetch-mappings.py.out

verifying c4dcdb393137 against file:///[\w/]*/testrepo-1/trunk@2 (re)
verifying 96b13d4b7db4 against file:///[\w/]*/testrepo-1/branches/badname@3 (re)
verifying c1795a0e0baf against file:///[\w/]*/testrepo-1/branches/feature@4 (re)
verifying c4dcdb393137 against file:///[\w/]*/testrepo-1/trunk@2 (re)
verifying 96b13d4b7db4 against file:///[\w/]*/testrepo-1/branches/badname@3 (re)
verifying c1795a0e0baf against file:///[\w/]*/testrepo-1/branches/feature@4 (re)
hgsubversion: migrate all the tests to silentrunner Summary: This migration allows `./run-tests.py` to run `hgsubversion` tests. Since hgsubversion tests are actually python unittests, we don't care about their output at all, they fail differently. But the behavior of the test suite require us to match whatever the tests prints. We do this later in the stack. Depends on D6719886 Test Plan: - check that tests are runnable at least Reviewers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D6719890 2018-01-17 14:23:44 +03:00			`verifying c4dcdb393137 against file:///[\w/]*/testrepo-1/trunk@2 (re)`
tests: fix hgsubversion tests Summary: Since D16681230, a commit made with no file changes will re-use it's parent manifest. This can trigger the commit hash to be different, which broke some subversion tests. Since hgsubversion will be going away soon, I took the approach of using run-tests.py -i and in test-hgsubversion-custom-layout.py to not run the test that fails. Reviewed By: sfilipco Differential Revision: D16836997 fbshipit-source-id: 58e50a9147c8c263fca74158af120ec8ec5d8c52 2019-08-16 01:46:26 +03:00			`verifying 96b13d4b7db4 against file:///[\w/]*/testrepo-1/branches/badname@3 (re)`
			`verifying c1795a0e0baf against file:///[\w/]*/testrepo-1/branches/feature@4 (re)`
hgsubversion: migrate all the tests to silentrunner Summary: This migration allows `./run-tests.py` to run `hgsubversion` tests. Since hgsubversion tests are actually python unittests, we don't care about their output at all, they fail differently. But the behavior of the test suite require us to match whatever the tests prints. We do this later in the stack. Depends on D6719886 Test Plan: - check that tests are runnable at least Reviewers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D6719890 2018-01-17 14:23:44 +03:00			`verifying c4dcdb393137 against file:///[\w/]*/testrepo-1/trunk@2 (re)`
tests: fix hgsubversion tests Summary: Since D16681230, a commit made with no file changes will re-use it's parent manifest. This can trigger the commit hash to be different, which broke some subversion tests. Since hgsubversion will be going away soon, I took the approach of using run-tests.py -i and in test-hgsubversion-custom-layout.py to not run the test that fails. Reviewed By: sfilipco Differential Revision: D16836997 fbshipit-source-id: 58e50a9147c8c263fca74158af120ec8ec5d8c52 2019-08-16 01:46:26 +03:00			`verifying 96b13d4b7db4 against file:///[\w/]*/testrepo-1/branches/badname@3 (re)`
			`verifying c1795a0e0baf against file:///[\w/]*/testrepo-1/branches/feature@4 (re)`