evolve: mark new hash-salting extras keys as uninteresting for effect flag The user doesn't care if the `evolve_source_local`/`evolve_source_other` values in the extras changed, so this patch adds them to the blacklist that already exists for that purpose. This should also fix the flakiness we've seen in some tests. The flakiness seemed to stem from `mercurial.obsutil.geteffectflag()` not sorting extras keys. That means we ran into it relatively often for the `evolve_source_local`/`evolve_source_other` keys because there were two of them. That sorting bug should be fixed upstream.

     1

Test that share-clones use the cache in the original repository.

     2

     3

  $ . $TESTDIR/testlib/common.sh

     4

     5

  $ hg init share-base

     6

  $ cd share-base/

     7

  $ cat >> .hg/hgrc <<EOF

     8

  > [extensions]

     9

  > evolve=

    10

  > share=

    11

  > EOF

    12

  $ hg debugbuilddag .+3:branchpoint+4*branchpoint+2

    13

  $ cd ..

    14

  $ hg --config extensions.share= share -U share-base share-client

    15

  $ cd share-client

    16

  $ hg debugupdatecache

    17

  $ test -d .hg/cache

    18

  [1]

    19

  $ test -d ../share-base/.hg/cache

    20