sapling/tests/test-repo-leak.t

216 lines
4.4 KiB
Perl
Raw Normal View History

Test native objects attached to the "repo" object gets properly released at the
end of process.
Attach an object with `__del__` to learn whether repo, ui are dropped on not.
$ cat > $TESTTMP/printondel.py << EOF
> class printondel(object):
> def __del__(self):
> print("__del__ called")
> def reposetup(ui, repo):
> obj = printondel()
> repo._deltest = obj
> ui._deltest = obj
> EOF
$ setconfig extensions.leakdetect=$TESTTMP/printondel.py
No leak without extensions
$ newrepo
__del__ called
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: blackbox
$ newrepo
__del__ called
$ setconfig extensions.blackbox=
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: remotefilelog
$ newrepo
__del__ called
$ echo remotefilelog >> .hg/requires
$ setconfig extensions.remotefilelog= remotefilelog.cachepath=$TESTTMP/cache
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: treemanifest and fastmanifest
$ newrepo
__del__ called
$ setconfig extensions.treemanifest= extensions.fastmanifest= remotefilelog.reponame=x
$ hg log -r . -T '{node}\n'
0000000000000000000000000000000000000000
__del__ called
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: treemanifest only
$ newrepo
__del__ called
$ setconfig extensions.treemanifest= treemanifest.treeonly=1 remotefilelog.reponame=x
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: hgsubversion
$ newrepo
__del__ called
$ setconfig extensions.hgsubversion=
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: sparse
$ newrepo
__del__ called
$ setconfig extensions.sparse=
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: commitcloud
$ newrepo
__del__ called
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ setconfig extensions.infinitepush= extensions.commitcloud=
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Fine extension: sampling
$ newrepo
__del__ called
$ setconfig extensions.sampling=
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
Somehow problematic: With many extensions
$ newrepo
__del__ called
$ echo remotefilelog >> .hg/requires
$ cat >> .hg/hgrc <<EOF
> [extensions]
> absorb=
> amend=
> arcdiff=
> automv=
> blackbox=
> checkmessagehook=
> chistedit=
> cleanobsstore=!
> clienttelemetry=
> clindex=
> color=
> commitcloud=
> conflictinfo=
> copytrace=
> crdump=
> debugcommitmessage=
> dialect=
> directaccess=
> dirsync=
> errorredirect=!
> extorder=
> extorder=
> fastannotate=
> fastlog=
> fastmanifest=
> fastpartialmatch=!
> fbconduit=
> fbhistedit=
> githelp=
> gitlookup=!
> gitrevset=!
> grpcheck=
> hgevents=
> hgsubversion=
> hiddenerror=
> histedit=
> infinitepush=
> journal=
> logginghelper=
> lz4revlog=
> mergedriver =
> mergedriver=
> morecolors=
> morestatus=
> myparent=
> patchrmdir=
> phabdiff=
> phabstatus=
> phrevset=
> progressfile=
> pullcreatemarkers=
> purge=
> pushrebase =
> pushrebase=
> rage=
> rebase =
> rebase=
> remotefilelog =
> remotefilelog=
> remotenames=
> reset=
> sampling=
> shelve=
> sigtrace=
> simplecache=
> smartlog=
> sparse=
> sshaskpass=
> stat=
> traceprof=
> treedirstate=
> treemanifest=
> tweakdefaults=
> undo=
>
> [phases]
> publish = False
>
> [remotefilelog]
> datapackversion = 1
> historypackv1 = True
> reponame = x
> cachepath = $TESTTMP/cache
>
> [treemanifest]
> treeonly=True
>
> [fbconduit]
> host=example.com
> path=/conduit/
> reponame=x
> EOF
$ hg log -r . -T '{manifest % "{node}"}\n'
0000000000000000000000000000000000000000
__del__ called
$ touch x
(this behaves differently with buck / setup.py build)
$ hg ci -m x -A x
__del__ called (?)
$ hg log -r . -T '{manifest % "{node}"}\n'
c2ffc254676c538a75532e7b6ebbbccaf98e2545
__del__ called