Skip to content
Snippets Groups Projects
  1. Jun 05, 2018
  2. Jun 04, 2018
  3. Jun 06, 2018
  4. May 24, 2018
    • Denis Laxalde's avatar
      transaction-summary: show phase changes statistics in pull/unbundle · eb9835014d20
      Denis Laxalde authored
      Upon pull or unbundle, we display a message with the number of
      changesets which phase became public. Noticeably, this new message would
      appear even if no new changeset were added (below the "no changes found"
      message), thus indicating that something actually happened to the local
      repository.
      eb9835014d20
  5. May 15, 2018
  6. May 01, 2018
  7. Apr 04, 2018
  8. Oct 12, 2017
    • Denis Laxalde's avatar
      transaction-summary: show the range of new revisions upon pull/unbundle (BC) · eb586ed5d8ce
      Denis Laxalde authored
      Upon pull or unbundle, we display a message with the range of new revisions
      fetched. This revision range could readily be used after a pull to look out
      what's new with 'hg log'. The algorithm takes care of filtering "obsolete"
      revisions that might be present in transaction's "changes" but should not be
      displayed to the end user.
      eb586ed5d8ce
  9. Jul 18, 2017
  10. Jul 16, 2017
  11. Jul 12, 2017
    • Boris Feld's avatar
      phases: test phases tracking at the transaction level · 67a3204c83c1
      Boris Feld authored
      Now that we have all tracking in place, the data in `tr.changes['phases']`
      dictionary should be correct and we should test it.
      
      It is a bit late in the cycle to discuss to add any public API (eg: hooks)
      that expose the data to the user, so we just add a small test extension
      displaying the data. It is enabled for the phases tests.
      
      New output have been manually checked for consistency.
      67a3204c83c1
  12. Oct 13, 2016
    • Pierre-Yves David's avatar
      changegroup: skip delta when the underlying revlog do not use them · 6b0741d6d234
      Pierre-Yves David authored
      Revlog can now be configured to store full snapshot only. This is used on the
      changelog. However, the changegroup packing was still recomputing deltas to be
      sent over the wire.
      
      We now just reuse the full snapshot directly in this case, skipping delta
      computation. This provides use with a large speed up(-30%):
      
      # perfchangegroupchangelog on mercurial
      ! wall 2.010326 comb 2.020000 user 2.000000 sys 0.020000 (best of 5)
      ! wall 1.382039 comb 1.380000 user 1.370000 sys 0.010000 (best of 8)
      
      # perfchangegroupchangelog on pypy
      ! wall 5.792589 comb 5.780000 user 5.780000 sys 0.000000 (best of 3)
      ! wall 3.911158 comb 3.920000 user 3.900000 sys 0.020000 (best of 3)
      
      # perfchangegroupchangelog on mozilla central
      ! wall 20.683727 comb 20.680000 user 20.630000 sys 0.050000 (best of 3)
      ! wall 14.190204 comb 14.190000 user 14.150000 sys 0.040000 (best of 3)
      
      Many tests have to be updated because of the change in bundle content. All
      theses update have been verified.  Because diffing changelog was not very
      valuable, the resulting bundle have similar size (often a bit smaller):
      
      # full bundle of mozilla central
      with delta:    1142740533B
      without delta: 1142173300B
      
      So this is a win all over the board.
      6b0741d6d234
  13. Aug 20, 2016
  14. Sep 20, 2016
  15. Aug 03, 2016
    • Pierre-Yves David's avatar
      tests: remove all remaining usage of experimental.bundle2-exp · 30c59bdd4f41
      Pierre-Yves David authored
      The only remaining usage of the experimental config were enforcing bundle2 on.
      These are very old remains of when bundle2 was off by default. This was also
      useful to highlight the fact that this was a bundle2 run and that a bundle1 one
      was nearby. However, we want a future developer working on bundle3 to notice
      possible output/behavior change on these tests and take them in account.  So we
      do not enforce bundle2 for these runs. We leave a comment around to make sure
      dev still notice the bundle1 version.
      30c59bdd4f41
    • Pierre-Yves David's avatar
      tests: use 'legacy.exchange' option in various mixed tests · ac9b85079122
      Pierre-Yves David authored
      The new option will stay around. The experimental option was only meant to be
      temporary. We update various tests that validate both bundle1 and bundle2
      version side by side. This changeset only takes care of enforcing bundle1. The
      other use of 'experimental.bundle2-exp=True' will be taken care of in the next
      changeset.
      ac9b85079122
  16. Aug 02, 2016
  17. Jan 13, 2016
  18. Dec 14, 2015
  19. Jun 08, 2015
  20. May 27, 2015
  21. Aug 15, 2014
    • Mads Kiilerich's avatar
      bundle: when verbose, show what takes up the space in the generated bundle · 4ab66de46a96
      Mads Kiilerich authored
      This is kind of similar to the debugbundle command but gives summarized actual
      uncompressed number of bytes when creating the bundle. The numbers are as
      usable as the bundle format is efficient. Hopefully bundle2 will make it a
      better indicator of actual entropy.
      
      This is useful when accepting pull requests to assess whether the repo size
      increase seems reasonable for the diff before pushing stuff upstream, It has
      helped me catching large files that should have been committed as largefiles
      but was committed as regular files in intermediate changesets.
      
      This output doesn't combine well with debug output so we only enable it when
      verbose without debug.
      4ab66de46a96
  22. Apr 17, 2014
  23. Aug 06, 2014
  24. Apr 13, 2014
  25. Jan 23, 2014
  26. Jan 28, 2013
  27. Nov 22, 2013
  28. Nov 15, 2013
  29. Oct 03, 2013
  30. May 02, 2013
  31. Apr 30, 2013
    • Pierre-Yves David's avatar
      push: make locking of source optional (issue3684) · 3f5e75c22585
      Pierre-Yves David authored
      Having the permission to lock the source repo on push is now optional. When the
      repo cannot be locked, phase are not changed locally. A status message is issue
      when some actual phase movement are skipped:
      
          cannot lock source repo, skipping local public phase update
      
      A debug message with the exact reason of the locking failure is issued in all
      case.
      3f5e75c22585
  32. Sep 14, 2012
  33. Aug 15, 2012
  34. Apr 27, 2012
  35. Apr 24, 2012
    • Pierre-Yves David's avatar
      branchmap: server should not advertise secret changeset in branchmap (Issue3303) · 39d1f83eb05d
      Pierre-Yves David authored
      Discovery now use an overlay above branchmap to prune invisible "secret"
      changeset from branchmap.
      
      To minimise impact on the code during the code freeze, this is achieve by
      recomputing non-secret heads on the fly when any secret changeset exists. This
      is a computation heavy approach similar to the one used for visible heads. But
      few sever should contains secret changeset anyway.  See comment in code for more
      robust approach.
      
      On local repo the wrapper is applied explicitly while the wire-protocol take
      care of wrapping branchmap call in a transparent way. This could be unified by
      the Peter Arrenbrecht and Sune Foldager proposal of a `peer` object.
      
      An inappropriate `(+i heads)` may still appear when pushing new changes on a
      repository with secret changeset. (see Issue3394 for details)
      39d1f83eb05d
  36. Feb 29, 2012
    • Pierre-Yves David's avatar
      bundlerepo: bundle repos should be non-publishing (issue3266) · 40cc20042fb4
      Pierre-Yves David authored
      Bundle repo contains both the bundle content and the content of the repository
      used as a base. This create bugs with phases exchange because the "remote"
      repository claim to contains changeset it does not. The easiest way to fix this
      bug is to ensure a bundle repo as non publishing. This way changeset will be
      seen in the same phase than locally.
      
      This patch does not alter in which phase bundle revision are seen. For now they
      are seen as if an old client had add them on the remote: They inherit their
      phase from parent whatever the parent is. This is to be fixed in a later patch
      40cc20042fb4
  37. Feb 10, 2012
Loading