D1933: repair: invalidate volatile sets after stripping

[mharbison72 (Matt Harbison)]

mharbison72 added a comment.


  That worked for me, thanks.
  
  FWIW, a couple of years ago, there were test failures in evolve on Windows that was fixed by adding a `repo.invalidate()` in bookmarks.py.  I can't find the thread now, and that fix wasn't taken.  So Windows may not be getting it all correct either.  That said, I just ran the evolve tests, and it seems to have disappeared.  (Though I haven't figured out how to run the tests on the repo reliably since it started supporting enabling with `evolve=`.  It seems to want to use the pip installed code.)  There are now missing orphan messages similar to above, but these have 'remote:' prefixes, so it's probably an issue of not being flushed, rather than an actual problem.
  
  If you need to throw patches at me to trace through the Windows code to see what's different, feel free.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D1933

To: martinvonz, durin42, #hg-reviewers
Cc: mharbison72, quark, mercurial-devel