facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-06 06:47:41 +03:00
Code Issues Projects Releases Wiki Activity
8c3c531f2c
sapling/eden/scm/tests/test-purge-fsmonitor.t

19 lines
358 B
Perl
Raw Normal View History

tests: add a test demonstrating watchman clock gets reset after purge --all Summary: With treestate, watchman clock is not expected to be reset. But `purge --all` bypasses some fsmonitor code paths and manages to reset the clock. Add a test to show that. Reviewed By: DurhamG Differential Revision: D10188142 fbshipit-source-id: 4524979fb96d41fab881b7ee44ad9fa854081b26
2018-10-13 05:20:49 +03:00
#require fsmonitor
$ newrepo
$ touch x
Watchman clock is set after "status"
$ hg status
? x
tests: replace print in debugshell with ui.write Summary: Similar to D18926784. Mercurial makes sure content written by `ui.write` is flushed, while there is no such guarantee for `print`. When running using chg, it's more likely that `print` content gets disappeared. Therefore let's use `ui.write` instead. Reviewed By: ikostia Differential Revision: D18926983 fbshipit-source-id: 960c189cc48bc3c89bb4f7993d2033dd45c52a67
2019-12-13 21:27:16 +03:00
$ hg debugshell -c 'ui.write("%s\n" % str(repo.dirstate.getclock()))'
tests: add a test demonstrating watchman clock gets reset after purge --all Summary: With treestate, watchman clock is not expected to be reset. But `purge --all` bypasses some fsmonitor code paths and manages to reset the clock. Add a test to show that. Reviewed By: DurhamG Differential Revision: D10188142 fbshipit-source-id: 4524979fb96d41fab881b7ee44ad9fa854081b26
2018-10-13 05:20:49 +03:00
c:* (glob)
fsmonitor: do not set watchman clock to None Summary: There are some code paths (ex. "purge --all") that sets watchman clock to None unexpectedly. That makes the next command slow. Bypass it by detecting the case and avoid setting clock to None. Reviewed By: DurhamG Differential Revision: D10188143 fbshipit-source-id: 4c35dfcee658ca2075d686da7d886e4b3a352b5a
2018-10-13 05:20:51 +03:00
Watchman clock is not reset after a "purge --all"
tests: add a test demonstrating watchman clock gets reset after purge --all Summary: With treestate, watchman clock is not expected to be reset. But `purge --all` bypasses some fsmonitor code paths and manages to reset the clock. Add a test to show that. Reviewed By: DurhamG Differential Revision: D10188142 fbshipit-source-id: 4524979fb96d41fab881b7ee44ad9fa854081b26
2018-10-13 05:20:49 +03:00
$ hg purge --all
tests: replace print in debugshell with ui.write Summary: Similar to D18926784. Mercurial makes sure content written by `ui.write` is flushed, while there is no such guarantee for `print`. When running using chg, it's more likely that `print` content gets disappeared. Therefore let's use `ui.write` instead. Reviewed By: ikostia Differential Revision: D18926983 fbshipit-source-id: 960c189cc48bc3c89bb4f7993d2033dd45c52a67
2019-12-13 21:27:16 +03:00
$ hg debugshell -c 'ui.write("%s\n" % str(repo.dirstate.getclock()))'
fsmonitor: do not set watchman clock to None Summary: There are some code paths (ex. "purge --all") that sets watchman clock to None unexpectedly. That makes the next command slow. Bypass it by detecting the case and avoid setting clock to None. Reviewed By: DurhamG Differential Revision: D10188143 fbshipit-source-id: 4c35dfcee658ca2075d686da7d886e4b3a352b5a
2018-10-13 05:20:51 +03:00
c:* (glob)
tests: add a test demonstrating watchman clock gets reset after purge --all Summary: With treestate, watchman clock is not expected to be reset. But `purge --all` bypasses some fsmonitor code paths and manages to reset the clock. Add a test to show that. Reviewed By: DurhamG Differential Revision: D10188142 fbshipit-source-id: 4524979fb96d41fab881b7ee44ad9fa854081b26
2018-10-13 05:20:49 +03:00
$ hg status
Reference in New Issue Copy Permalink