Skip to content
Snippets Groups Projects
  1. Jan 30, 2018
    • Matt Harbison's avatar
      lfs: emit a status message to indicate how many blobs were uploaded · fa993c3c8462
      Matt Harbison authored
      Previously, there was a progress bar indicating the byte count, but then it
      disappeared once the transfer was done.  Having that value stay on the screen
      seems useful.  Downloads are done one at a time, so hold off on that until they
      can be coalesced, to avoid a series of lines being printed.  (I don't have any
      great ideas on how to do that.  It would be a shame to have to wrap a bunch of
      read commands to be able to do this.)
      
      I'm not sure if the 'lfs:' prefix is the right thing to do here.  The others in
      the test are verbose/debug messages, so in the normal case, this is the only
      line that's prefixed.
      fa993c3c8462
  2. Jan 31, 2018
  3. Feb 01, 2018
  4. Jan 18, 2018
  5. Feb 01, 2018
  6. Jan 18, 2018
  7. Jan 31, 2018
  8. Jan 26, 2018
  9. Jan 25, 2018
  10. Jan 31, 2018
  11. Feb 01, 2018
  12. Jan 31, 2018
    • Gregory Szorc's avatar
      tests: allow [Errno] in output · 2f7ab4fb7711
      Gregory Szorc authored
      I'm not sure why, but my system is printing "[Errno -5]" before
      the "No address associated with hostname" message. I suspect a
      modern version of Python improved errno tracking or something.
      
      Add an "[Errno ...]" pattern as optional output to make the test
      pass.
      
      Differential Revision: https://phab.mercurial-scm.org/D1958
      2f7ab4fb7711
  13. Jan 26, 2018
  14. Jan 25, 2018
  15. Feb 01, 2018
    • Martin von Zweigbergk's avatar
      setdiscovery: don't call "heads" wire command when heads specified · 5cfdf6137af8
      Martin von Zweigbergk authored
      Our custom server has too many heads to announce (one per code review,
      plus a public head), but it still lets the user request one of them by
      doing
      
        hg pull -r <some expression>
      
      After the client has resolved the expression to a set of nodeids by
      calling the "lookup" wire command, it will start the discovery
      phase. Before this patch, that doesn't take the requested heads into
      account and unconditionally calls the server's "heads" command to find
      all its heads. One consequence of that the "all remote heads known
      locally" case triggers if the client already had the public head and
      the user will see a "no changes found" message that's unrelated to the
      head they requested. That message confused me for a while. More
      imporantly, it also means that pullop.cgresult incorrectly (given our
      arguably misbehaving server) gets set to 0 (no changesets added),
      which confused some of our extensions.
      
      This patch makes it so the client skips the "heads" command if the
      user requested specific revisions.
      
      Since the "heads" command is normally batched with the first "known"
      command and calculating the list of heads is probably cheap, I don't
      expect much improvement in speed from this.
      
      Differential Revision: https://phab.mercurial-scm.org/D1962
      5cfdf6137af8
    • Martin von Zweigbergk's avatar
      testrunner: on error, color the "(case xxx)" part the same as filename · 8a7140ec4c89
      Martin von Zweigbergk authored
      When using #testcases, the lines that read something like
      
        ERROR: test-split.t (case obsstore-off) output changed
      
      get colored red and the filename gets highlighted with a brighter
      red. This makes it harder to notice the "case obsstore-off" part, but
      it does seem important, so let's highlight it.
      
      Differential Revision: https://phab.mercurial-scm.org/D1959
      8a7140ec4c89
  16. Jan 18, 2018
Loading