Mercurial > hg
view tests/blacklists/fsmonitor @ 42211:20fce2742399
tests: slightly modify a linkrev test to prepare for expanding it
The test case checks that the copy tracing code doesn't get confused
by linkrevs when walking a file's ancestors. This patch chnages the
test slightly so a second commit is grafted, thus producing a second
"bad" linkrev. I'll use this in the next patch to demonstrate a bug.
Differential Revision: https://phab.mercurial-scm.org/D6321
author | Martin von Zweigbergk <martinvonz@google.com> |
---|---|
date | Sat, 27 Apr 2019 22:57:15 -0700 |
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