Summary: They will be replaced by successors and predecessors.
Reviewed By: singhsrb
Differential Revision: D14000097
fbshipit-source-id: 07f0c97edd7eb16ad665c00886c00212d516ae72
Summary:
Rewrite "graft --force" and "empty graft" test cases to not depend on the
previous repo state. Remove the "same origin policy" test since eventually
we'll use mutation history to test origins and the code path here would be
rewritten.
This makes it easier to change the rest of the test.
Differential Revision: D14000100
fbshipit-source-id: 26002774c370a965a9bca157e08246c89aa5e274
Summary:
The test has many problems. Namely, it depends too much on previous repo state,
uses legacy features like named branches, revision numbers, unsafe strip, and rollback,
and is too verbose and over-testing a lot of things (ex. test commit template
many times, test diff output many times, test bundle debug output
unnecessarily, etc).
Rewrite the test to solve all of the above issues:
- Every individual test case uses separate small repos.
- Do not use revision numbers.
- Do not use legacy strip.
- Do not use named branch.
This also reveals that amending a merge commit is buggy in many ways. We can
probably fix them up when cleaning up the commit/merge logic.
Differential Revision: D13993825
fbshipit-source-id: 9e1ff8054741b4356319ce37daea3c5184933927
Summary:
The use of branches is only to create a merge commit. Use drawdag to do that
instead.
Differential Revision: D13993829
fbshipit-source-id: b5f217e7d9ba535b7fd379ec4ca31b899350de02
Summary:
The test is mainly about warnings of new heads, which we might want to remove
entirely (see D8148016). The test is also deeply coupled with named branches,
which will be removed.
Differential Revision: D13993828
fbshipit-source-id: 950f0cb98cd6cb2c8192f1ff36ce2d6b642d1225
Summary:
test-tag.t uses named branches too much. Since global tags are also going away,
replace the test with a simple one about local tags. The local tag portion in
test-tag.t is not too much, though.
Differential Revision: D13993827
fbshipit-source-id: b3a86fa1e07b945fc2926f00ef9de31a4506ba37
Summary:
Rewrite the test:
- Use drawdag to create test repos.
- Use commit hash instead of revision numbers for new test cases.
- Remove unrelated test cases (ex. strip, branch heads).
- Remove use of named branch.
Differential Revision: D13993823
fbshipit-source-id: d20954dec1b39313f08699f796d5db167dfee641
Summary:
The "cache" refers to branch and tag caches. Both of them are planned for
removal. Therefore remove the test.
Reviewed By: singhsrb
Differential Revision: D13978569
fbshipit-source-id: 8593f54af4ecd3fb759d2a3a0fe00eb9d8505112
Summary:
`test-patchbomb.t` uses named branches and does not look simple to fix.
We don't use email patches internally, and it's not hard to write scripts
around `hg export`. Therefore drop the extension and its tests.
Reviewed By: singhsrb
Differential Revision: D13978577
fbshipit-source-id: 19867ae68c19c996bfce064eb2234705939db9ea
Summary:
The test uses named branches so it will break without modification in the
future. Since bundle1 and ssh are "unloved" features, remove the test instead
of fixing it.
Reviewed By: singhsrb
Differential Revision: D13978573
fbshipit-source-id: d5446685056457766d1752446de9d842f40f3ebf
Summary:
The test uses named branches extensively, partically because there are multiple
ways to specify where to update:
hg clone URL#NAME1 -b NAME2 -u NAME3
^^^^^^ ^^^^^ ^^^^^
branch name | |
branch name, again! |
revset, can also be a branch name
In the long run, we'll kill NAME1 (`#...` syntax) and NAME2 (`clone -b` flag).
So the (undesirable) complexity will be gone. Remove the test to make the
transition easier.
The `clone -u REV` feature is still tested in `test-clone.t`.
Reviewed By: singhsrb
Differential Revision: D13978578
fbshipit-source-id: 839ad39779c4526e4be48e133610bdb46f57fc93
Summary: This makes it compatible with future releases.
Reviewed By: singhsrb
Differential Revision: D13978572
fbshipit-source-id: 9394a811b848f1160aaa54be0d09dfc2ea142e81
Summary: Named branches are going away. Remove the logic around it.
Reviewed By: phillco
Differential Revision: D13978575
fbshipit-source-id: d6e28d7cadffa612f74a2afc12800829d6113dfa
Summary:
The test uses branches to name commits server-side and isolate them from the
bookmark namespace. Branches are going away. Use local tags instead.
Reviewed By: phillco
Differential Revision: D14057253
fbshipit-source-id: 33b8ab63027042eb5e244187874190bdd31e62d1
Summary:
The test uses named branches heavily. It seems the test just wants to make
sure remotenames work with the schemes extension. Rewrite it to stop using
named branches.
Reviewed By: singhsrb
Differential Revision: D13978570
fbshipit-source-id: 3d0f284bb2398da0283b3bf5a06d879182a70d84
Summary:
Purging of packs may happen before the repack operation, and when loosefiles
are also present, repack will reconstruct the packs from them. By forcing a
packsonly, we won't have a chance of reconstructing the purged ones.
Differential Revision: D14013788
fbshipit-source-id: d77d9ec2b9c5a086caaf9164a8ac56dd7d1e1255
Summary:
The refresh function is intended to load on-disk packfiles that aren't yet
present in the cache, but it had several issues that resulted in unexpected
behavior. Mainly, the new files would be added in the wrong order in the cache,
and runonpacks would not update the last used packs.
Differential Revision: D14013785
fbshipit-source-id: da4151b859441f0ba51863f3907852922c255f82
Summary:
This should auto recover from a state where watchman returns too many files,
which makes "hg status" slow.
The default config value 200 is not chosen very scientifically, but it should
cover the 6s status case where there are 90k changed files reported.
Differential Revision: D14036494
fbshipit-source-id: 368f53e99e2e54343a6ac9145cbb86e4ac65e4ac
Summary:
akushner encountered a case where "hg status" takes 5+ seconds and cannot
self-recover. That is because watchman constantly returns huge number of files
and fsmonitor didn't choose to update the clock to address that.
Reviewed By: DurhamG
Differential Revision: D14036493
fbshipit-source-id: 0bd8f7c9e3a51b6b4d2a1584b68883f8579e3f0f
Summary: This is caused by D13516212, and not covered by tests.
Reviewed By: DurhamG, StanislavGlebik
Differential Revision: D14025817
fbshipit-source-id: 8a529085c40c5d2ae17ccf3de1ccea22c8d7dbd2
Summary: It is unavailable on OSX, but we have a custom implementation.
Reviewed By: DurhamG
Differential Revision: D14028103
fbshipit-source-id: 4b6916792fc9da43795b0f9db57ec2a057c92283
Summary:
The test is about treating the "default" remote branch specially.
Named branches are going away, therefore delete the test.
Reviewed By: ikostia
Differential Revision: D13976850
fbshipit-source-id: 0283e78c120efd0cf9c91811b823923780cdbfd9
Summary:
The test uses named branch. Since subrepo is also on the list to kill, just
remove the test now.
Differential Revision: D13954459
fbshipit-source-id: 29e8009376081d964441497796fda3490f2137e3
Summary:
The test was about the connection handling between remotefilelog and
fastannotate. It uses named branch to test certain code paths, which
is not trivial to migrate off.
We'll probably rework the protocol used here and maybe do something very
different regarding on linelog with Mononoke. Therefore just remove the
test for now.
Reviewed By: singhsrb
Differential Revision: D13934435
fbshipit-source-id: 9ba0b760ba17efd3ede6de7612e6532f3d13a4f8
Summary:
The test was relying on the ability to merge a "fast-forward" commit, it's no
longer possible without named branches. So the DAG was changed from two linear
commits to "Y"-ish 3 commits.
This makes the test future-proof.
Differential Revision: D13954460
fbshipit-source-id: 944747404843e985f06d18fe0618843dca64630f
Summary: This test was broken by D13980892 and needs to be updated.
Reviewed By: DurhamG
Differential Revision: D14001840
fbshipit-source-id: 6487159445f8aa049996a35e1bb70dad5af614ac
Summary: Size is not always the same, let just use number of files.
Reviewed By: rlangst
Differential Revision: D14004261
fbshipit-source-id: 13e21d8fd95ee09fc54c750ceecc48bcd484bc9e
Summary:
this fixes `hg-new-workdir` by matching the function signature
and propagating the arguments.
Reviewed By: singhsrb
Differential Revision: D13992348
fbshipit-source-id: 582025affe2e0511f239e82bc880b2fecea84ac7
Summary:
previously, unexpected output would cause the harness to
stack trace and not show the actual test failure.
This catches the error and treats it as a failed run, which causes
the test output to be displayed.
No more `ValueError: invalid literal for int() with base 10: '0\xe2\x90\x8a'`
Reviewed By: DurhamG
Differential Revision: D13995000
fbshipit-source-id: 5c1a9e8d6f8e81a924cdbf760fa75cdc0d33b74d
Summary:
Change the test to avoid creating branches so it could still work
once `hg branch` gets removed.
Differential Revision: D13954467
fbshipit-source-id: ec6ee3430cecd4ee4daa23b303f0a36be9198659
Summary:
Change the test to not create branches, so it could still work
once `hg branch` gets removed.
Differential Revision: D13954465
fbshipit-source-id: 10ff86b2a765cb8bd57d1589a4e3624d553b4d07
