mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 00:14:35 +03:00
82b7f72254
Facebook has developed an extension to enable "sparse" checkouts - a working directory with a subset of files. This feature is a critical component in enabling repositories to scale to infinite number of files while retaining reasonable performance. It's worth noting that sparse checkout is only one possible solution to this problem: another is virtual filesystems that realize files on first access. But given that virtual filesystems may not be accessible to all users, sparse checkout is necessary as a fallback. Per mailing list discussion at https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-March/095868.html we want to add sparse checkout to the Mercurial distribution via roughly the following mechanism: 1. Vendor extension as-is with minimal modifications (this patch) 2. Refactor extension so it is more clearly experimental and inline with Mercurial practices 3. Move code from extension into core where possible 4. Drop experimental labeling and/or move feature into core after sign-off from narrow clone feature owners This commit essentially copies the sparse extension and tests from revision 71e0a2aeca92a4078fe1b8c76e32c88ff1929737 of the https://bitbucket.org/facebook/hg-experimental repository. A list of modifications made as part of vendoring is as follows: * "EXPERIMENTAL" added to module docstring * Imports were changed to match Mercurial style conventions * "testedwith" value was updated to core Mercurial special value and comment boilerplate was inserted * A "clone_sparse" function was renamed to "clonesparse" to appease the style checker * Paths to the sparse extension in tests reflect built-in location * test-sparse-extensions.t was renamed to test-sparse-fsmonitor.t and references to "simplecache" were removed. The test always skips because it isn't trivial to run it given the way we currently run fsmonitor tests * A double empty line was removed from test-sparse-profiles.t There are aspects of the added code that are obviously not ideal. The goal is to make a minimal number of modifications as part of the vendoring to make it easier to track changes from the original implementation. Refactoring will occur in subsequent patches.
45 lines
1.2 KiB
Perl
45 lines
1.2 KiB
Perl
This test doesn't yet work due to the way fsmonitor is integrated with test runner
|
|
|
|
$ exit 80
|
|
|
|
test sparse interaction with other extensions
|
|
|
|
$ hg init myrepo
|
|
$ cd myrepo
|
|
$ cat > .hg/hgrc <<EOF
|
|
> [extensions]
|
|
> sparse=
|
|
> strip=
|
|
> EOF
|
|
|
|
Test fsmonitor integration (if available)
|
|
TODO: make fully isolated integration test a'la https://github.com/facebook/watchman/blob/master/tests/integration/WatchmanInstance.py
|
|
(this one is using the systemwide watchman instance)
|
|
|
|
$ touch .watchmanconfig
|
|
$ echo "ignoredir1/" >> .hgignore
|
|
$ hg commit -Am ignoredir1
|
|
adding .hgignore
|
|
$ echo "ignoredir2/" >> .hgignore
|
|
$ hg commit -m ignoredir2
|
|
|
|
$ hg sparse --reset
|
|
$ hg sparse -I ignoredir1 -I ignoredir2 -I dir1
|
|
|
|
$ mkdir ignoredir1 ignoredir2 dir1
|
|
$ touch ignoredir1/file ignoredir2/file dir1/file
|
|
|
|
Run status twice to compensate for a condition in fsmonitor where it will check
|
|
ignored files the second time it runs, regardless of previous state (ask @sid0)
|
|
$ hg status --config extensions.fsmonitor=
|
|
? dir1/file
|
|
$ hg status --config extensions.fsmonitor=
|
|
? dir1/file
|
|
|
|
Test that fsmonitor ignore hash check updates when .hgignore changes
|
|
|
|
$ hg up -q ".^"
|
|
$ hg status --config extensions.fsmonitor=
|
|
? dir1/file
|
|
? ignoredir2/file
|