sapling/tests/test-purge-fsmonitor.t

#require fsmonitor

  $ newrepo
  $ enable purge
  $ touch x

Watchman clock is set after "status"

  $ hg status
  ? x
  $ hg debugshell -c 'print(repo.dirstate.getclock())'
  c:* (glob)

Watchman clock is not reset after a "purge --all"

  $ hg purge --all
  $ hg debugshell -c 'print(repo.dirstate.getclock())'
  c:* (glob)
  $ hg status
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`
			`$ enable purge`
			`$ touch x`

			`Watchman clock is set after "status"`

			`$ hg status`
			`? x`
			`$ hg debugshell -c 'print(repo.dirstate.getclock())'`
			`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`
			`$ hg debugshell -c 'print(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`