largefiles: use 'default' instead of 'default-push' when pulling (issue3584) This only applies to downloading largefiles, and only when no source for the pull is explicitly provided. The repository itself was properly being pulled via 'default' previously. Using --all-largefiles is not necessary on a bare pull to test this (this existing test is merely a convenience), but it is required to test pulling on the rebase path. Note that the errors generated in the --rebase case are because the repo specified doesn't have the largefiles in its cache (though they are in the user cache), so the errors are misleading. Specifying --all-largefiles when cloning to 'b' fixes this, but instead of errors, it reports caching only 5 largefiles instead of the 9 that come up missing. Likely this is because the largefile download procedure tries to download missing files for each rev, and some of the files have standins in more than one rev that gets pulled.

     1

# invalid filenames

     2

test-add.t

     3

test-init.t

     4

test-clone.t

     5

test-contrib.t

     6

test-hgweb-raw.t

     7

test-walk.t

     8

     9

# no sockets or fifos

    10

test-hup.t

    11

test-inotify-debuginotify.t

    12

test-inotify-dirty-dirstate.t

    13

test-inotify-issue1208.t

    14

test-inotify-issue1371.t

    15

test-inotify-issue1542.t

    16

test-inotify-lookup.t

    17

test-inotify.t

    18

test-inotify-issue1556.t

    19

    20

# no hardlinks

    21

test-hardlinks.t

    22

test-relink.t

    23

    24

# exec bit problems

    25

test-convert-bzr-114.t

    26

test-convert-bzr-directories.t

    27

test-convert-bzr-merges.t

    28

test-convert-bzr-treeroot.t

    29

test-convert-darcs.t

    30

test-merge-tools.t

    31

    32

# debugstate exec bit false positives

    33

test-dirstate.t

    34

test-filebranch.t

    35

test-merge-remove.t