sapling/tests/test-filecache.py.out

basic:

creating
creating
creating
creating

fakeuncacheable:

creating
creating
creating
creating
creating
creating
repository tip rolled back to revision -1 (undo commit)
working directory now based on revision -1
repository tip rolled back to revision -1 (undo commit)
working directory now based on revision -1
scmutil: introduce filecache The idea is being able to associate a file with a property, and watch that file stat info for modifications when we decide it's important for it to be up-to-date. Once it changes, we recreate the object. On filesystems that can't uniquely identify a file, we always recreate. As a consequence, localrepo.invalidate() will become much less expensive in the case where nothing changed on-disk. 2011-07-09 20:06:59 +04:00			`basic:`

			`creating`
			`creating`
			`creating`
			`creating`

			`fakeuncacheable:`

			`creating`
			`creating`
			`creating`
			`creating`
			`creating`
			`creating`
destroyed: keep the filecache in sync with __dict__ (issue3335) (issue3693) (issue3743) We need to make sure that if X is in the filecache then it's also in the filecache owner's __dict__, otherwise it will go out of sync: repo.X # first access to X, records stat info in # filecache and updates __dict__ repo._filecache.clear() # removes X from _filecache but it's still in __dict__ repo.invalidate() # iterates over _filecache and removes entries # from __dict__, but X isn't in _filecache, so # it's kept in __dict__ repo.X # X is fetched from __dict__, bypassing the filecache 2013-01-09 22:37:44 +04:00			`repository tip rolled back to revision -1 (undo commit)`
			`working directory now based on revision -1`
			`repository tip rolled back to revision -1 (undo commit)`
			`working directory now based on revision -1`