Skip to content
Snippets Groups Projects
  1. Jun 06, 2018
    • Boris Feld's avatar
      shelve: no longer strip internal commit when using internal phase · 52dfa1eb0ad4
      Boris Feld authored
      When the internal phase is used, the internal commits we create during shelve
      will be automatically hidden, and we don't need to strip them. Avoiding strips
      gives much better performances and is less traumatic for caches.
      
      Test changes are all related to revision numbers increasing more quickly since
      we avoid stripping.
      
      At the end of `test-shelve.t` we now need manually strip the shelve-commit in
      addition to the x.shelve file deletion. This emulates a preexisting shelve
      after a repository upgrade.
      
      Note:
      
          The hidden internal commits confuses rebase a bit as shown by a new test
          added. This will happen when the user have shelve commits on top of a
          changeset to be rebased.
      
          We'll fix this in the next commit. As we still use a backup bundle, rebase
          can just strip the internal changesets and be fine.
      52dfa1eb0ad4
  2. Sep 19, 2018
  3. Sep 21, 2018
    • Matt Harbison's avatar
      run-tests: partially backout PYTHON quoting · 38d51371792b
      Matt Harbison authored
      In 7f8b7a060584, I quoted this to support python being installed to
      "Program Files".  Even though the string passed to os.popen() is this:
      
          "c:/Python27/python.exe" -c "import mercurial; print (mercurial.__path__[0])"
      
      ... cmd.exe is trying to run this:
      
          'c:/Python27/python.exe" -c "import'
      
      This caused test-hghave.t to fail, reporting 'unexpected mercurial lib: ""',
      because the failed execution prints nothing to stdout.  Py3 fails as though it's
      not quoted.  For whatever reason, print() shows up in the output when run with
      py2, but not py3, so I'm having a hard time debugging this.  For now, let's fix
      the buildbot.
      38d51371792b
  4. Sep 20, 2018
  5. Sep 19, 2018
  6. Sep 15, 2018
  7. Sep 20, 2018
  8. Sep 17, 2018
    • Anton Shestakov's avatar
      bundle2: make server.bundle2.stream default to True · 4bd6e444c76f
      Anton Shestakov authored
      Support for bundle2 streaming clones has been shipped in Mercurial 4.5
      (7eedbd5d4880), but was never activated by default. It's time to have more
      people use it. The new format allows streaming clones to transport cache
      (hooray for speed) and phaseroots (fixes phase-related issues).
      
      Changes in tests:
      
      bundle2 capabilities now have "stream=v2" (plus a '\n' as a separator) and
      therefore take 14 bytes more: "%0Astream%3Dv2". Tip for tests that have data
      encoded with CBOR: 0xd3 - 0xc5 = 14.
      
      $USUAL_BUNDLE2_CAPS$ replaces $USUAL_BUNDLE2_CAPS_SERVER$, which is the same
      thing, but without "stream=v2".
      
      Since streaming clones now also transfer caches, the reported byte and file
      counts are higher (e.g. 816 bytes in 9 files instead of 613 bytes in 4 files,
      a bit of --debug and manual math confirms that the caches take these extra 203
      bytes in 5 files).
      
      Differential Revision: https://phab.mercurial-scm.org/D4680
      4bd6e444c76f
    • Anton Shestakov's avatar
  9. Sep 20, 2018
  10. Sep 18, 2018
  11. Sep 20, 2018
    • Martin von Zweigbergk's avatar
      fastannotate: process files as they arrive · d8a7690ccc74
      Martin von Zweigbergk authored
      peer.commandexecutor()'s context manager waits for all responses to
      arrive in its __exit__() method. We want to process the results as
      they arrive, so we should do that inside the context manager
      scope. Note that the futures' result() methods have been replaced to
      make sure that the command executor's sendcommands() method is called
      when the first future's result is requested, so we don't need to do
      that.
      
      A minor side-effect is that we can no longer easily tell when the
      server has started sending us responses, so that long statement was
      lost.
      
      Differential Revision: https://phab.mercurial-scm.org/D4666
      d8a7690ccc74
  12. Sep 19, 2018
  13. May 22, 2018
    • Sean Farley's avatar
      memctx: simplify _manifest with new revlog nodeids · a5dafefc4a53
      Sean Farley authored
      This was originally written before we had modifiednodeid and
      addednodeid, so we had to get the parents of the context, the data from
      the function, and then hash that.
      
      This is much more simple now and helps refactor more code later.
      a5dafefc4a53
    • Sean Farley's avatar
      context: remove unused overlayfilectx (API) · 15e86ecf6b26
      Sean Farley authored
      It seems that this was maybe used in an extension but at this point
      nothing in lfs, hg-experimental, or any other cursory repo looked at has
      a reference to this class; so, for now, let's just remove it.
      15e86ecf6b26
  14. Jun 12, 2018
  15. Jul 18, 2018
    • Sean Farley's avatar
      filectx: fix return of renamed · 7375a9ab0149
      Sean Farley authored
      How is this not blowing up everywhere?
      
      It seems that filelog.renamed has always returned False (incorrectly a
      boolean) instead of the assumed None. Tracing through history, you need
      to skip over my move of code in 2013 by annotating from 896193a9cab4^
      and you can see the original code is from 2007 (180a3eee4b75) and that
      ab9fa7a85dd9 broke this by assuming renamed was a bool (instead of
      None).
      
      Refactoring memctx code later exposed this bug.
      7375a9ab0149
  16. Sep 19, 2018
  17. Sep 03, 2018
Loading