Mercurial > hgsubversion
view tests/fixtures/empty_dir_in_trunk_not_repo_root.svndump @ 1539:0ebcc5bbf692
tests: when making a `memctx`, make sure to use a single repo instance
The way self.repo is dynamic produces bad lock behavior because the
`context.memctx` ends up with a different instance than self in
`localrepo.commitctx`, which means the callbacks in the `memctx` get
an unlocked repo instance. This causes lock warning failures. When
it's not a code freeze for core, we should probably:
* Make lock failures hard, not just warnings
* Stop holding a repo reference in memctx, or otherwise check it's the same
instance as `self` during `localrepo.commitctx`
That's my best guess based on the (very hard to debug) test failures here.
| author | Augie Fackler <raf@durin42.com> |
|---|---|
| date | Sat, 28 Oct 2017 21:34:52 -0400 |
| parents | 6ec5b5fc5b4d |
| children |
line wrap: on
line source
SVN-fs-dump-format-version: 2 UUID: c866b883-4c03-404b-8609-dade481701a6 Revision-number: 0 Prop-content-length: 56 Content-length: 56 K 8 svn:date V 27 2009-04-15T03:39:30.544797Z PROPS-END Revision-number: 1 Prop-content-length: 104 Content-length: 104 K 7 svn:log V 5 trunk K 10 svn:author V 5 durin K 8 svn:date V 27 2009-04-15T03:39:31.069518Z PROPS-END Node-path: project Node-kind: dir Node-action: add Prop-content-length: 10 Content-length: 10 PROPS-END Node-path: project/trunk Node-kind: dir Node-action: add Prop-content-length: 10 Content-length: 10 PROPS-END Revision-number: 2 Prop-content-length: 118 Content-length: 118 K 7 svn:log V 18 file and empty dir K 10 svn:author V 5 durin K 8 svn:date V 27 2009-04-15T03:39:32.069497Z PROPS-END Node-path: project/trunk/a Node-kind: file Node-action: add Prop-content-length: 10 Text-content-length: 2 Text-content-md5: 60b725f10c9c85c70d97880dfe8191b3 Content-length: 12 PROPS-END a Node-path: project/trunk/narf Node-kind: dir Node-action: add Prop-content-length: 10 Content-length: 10 PROPS-END