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.
#require unix-permissions
Test that sqlite3 cache files inherit the permissions of the .hg
directory like other cache files.
$ . $TESTDIR/testlib/common.sh
$ cat << EOF >> $HGRCPATH
> [extensions]
> evolve =
> EOF
$ hg init test
$ cd test
$ chmod 700 .hg
$ hg debugupdatecache
$ ls -l .hg/cache/evoext_*.sqlite
-rw------- * .hg/cache/evoext_obshashrange_v2.sqlite (glob)
-rw------- * .hg/cache/evoext_stablerange_v2.sqlite (glob)
$ rm -r .hg/cache
$ chmod 770 .hg
$ hg debugupdatecache
$ ls -l .hg/cache/evoext_*.sqlite
-rw-rw---- * .hg/cache/evoext_obshashrange_v2.sqlite (glob)
-rw-rw---- * .hg/cache/evoext_stablerange_v2.sqlite (glob)
$ rm -r .hg/cache
$ chmod 774 .hg
$ hg debugupdatecache
$ ls -l .hg/cache/evoext_*.sqlite
-rw-rw-r-- * .hg/cache/evoext_obshashrange_v2.sqlite (glob)
-rw-rw-r-- * .hg/cache/evoext_stablerange_v2.sqlite (glob)