Mercurial > hg-stable
view tests/blacklists/fsmonitor @ 40847:77173267878b
narrow: don't resurrect old commits when narrowing (don't strip obsmarkers)
If you have an old obsolescence-chain of commits that has been pruned
and you narrow your repo so that some of those commits get stripped
(because they affected the removed paths), then we would currently
resurrect the commit that came before (along the obsmarker chain) the
last stripped commit. That happens by the usual rules for
obsmarker-stripping. However, it's quite surprising when it happens
when you narrow your repo. This patch makes narrowing not strip
obsmarkers.
Differential Revision: https://phab.mercurial-scm.org/D5364
author | Martin von Zweigbergk <martinvonz@google.com> |
---|---|
date | Mon, 03 Dec 2018 16:56:09 -0800 |
parents | 7a15cae3ec81 |
children |
line wrap: on
line source
# Blacklist for a full testsuite run with fsmonitor enabled. # Used by fsmonitor-run-tests. # The following tests all fail because they either use extensions that conflict # with fsmonitor, use subrepositories, or don't anticipate the extra file in # the .hg directory that fsmonitor adds. #### mainly testing eol extension test-eol-add.t test-eol-clone.t test-eol-hook.t test-eol-patch.t test-eol-tag.t test-eol-update.t test-eol.t test-eolfilename.t #### mainly testing largefiles extension test-issue3084.t test-largefiles-cache.t test-largefiles-misc.t test-largefiles-small-disk.t test-largefiles-update.t test-largefiles-wireproto.t test-largefiles.t test-lfconvert.t #### mainly testing nested repositories test-nested-repo.t test-push-warn.t test-subrepo-deep-nested-change.t test-subrepo-recursion.t test-subrepo.t #### fixing these seems redundant, because these don't focus on #### operations in the working directory or .hg test-debugextensions.t test-extension.t test-help.t