view tests/test-filelog.py.out @ 44999:d1471dbbdd63

merge: don't grab wlock when merging in memory I noticed this because we have an internal extension that does an in-memory rebase while holding only a repo lock, which resulted in a developer warning about the working copy lock being taken after the repo lock. Differential Revision: https://phab.mercurial-scm.org/D8665
author Martin von Zweigbergk <martinvonz@google.com>
date Wed, 24 Jun 2020 23:17:56 -0700
parents d76ba2090e0c
children
line wrap: on
line source

ERROR: FIXME: This is a known failure of filelog.size for data starting with \1\n
OK.