perf: clear vfs audit_cache before each run When generating a stream clone, we spend a large amount of time auditing path. Before this changes, the first run was warming the vfs cache for the other runs, leading to a large runtime difference and a "faulty" reported timing for the operation. We now clear this important cache between run to get a more realistic timing. Below are some example of median time change when clearing these cases. The maximum time for a run did not changed significantly. ### data-env-vars.name = mozilla-central-2018-08-01-zstd-sparse-revlog # benchmark.name = hg.perf.exchange.stream.generate # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default # benchmark.variants.version = latest no-clearing: 17.289905 cache-clearing: 21.587965 (+24.86%, +4.30) ## data-env-vars.name = mozilla-central-2024-03-22-zstd-sparse-revlog no-clearing: 32.670748 cache-clearing: 40.467095 (+23.86%, +7.80) ## data-env-vars.name = mozilla-try-2019-02-18-zstd-sparse-revlog no-clearing: 37.838858 cache-clearing: 46.072749 (+21.76%, +8.23) ## data-env-vars.name = mozilla-unified-2024-03-22-zstd-sparse-revlog no-clearing: 32.969395 cache-clearing: 39.646209 (+20.25%, +6.68) In addition, this significantly reduce the timing difference between the performance command, from the perf extensions and a `real `hg bundle` call producing a stream bundle. Some significant differences remain especially on the "mozilla-try" repositories, but they are now smaller. Note that some of that difference will actually not be attributable to the stream generation (like maybe phases or branch map computation). Below are some benchmarks done on a currently draft changeset fixing some unrelated slowness in `hg bundle` (34a78972af409d1ff37c29e60f6ca811ad1a457d) ### data-env-vars.name = mozilla-central-2018-08-01-zstd-sparse-revlog # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default hg.perf.exchange.stream.generate: 21.587965 hg.command.bundle: 24.301799 (+12.57%, +2.71) ## data-env-vars.name = mozilla-central-2024-03-22-zstd-sparse-revlog hg.perf.exchange.stream.generate: 40.467095 hg.command.bundle: 44.831317 (+10.78%, +4.36) ## data-env-vars.name = mozilla-unified-2024-03-22-zstd-sparse-revlog hg.perf.exchange.stream.generate: 39.646209 hg.command.bundle: 45.395258 (+14.50%, +5.75) ## data-env-vars.name = mozilla-try-2019-02-18-zstd-sparse-revlog hg.perf.exchange.stream.generate: 46.072749 hg.command.bundle: 55.882608 (+21.29%, +9.81) ## data-env-vars.name = mozilla-try-2023-03-22-zlib-general-delta hg.perf.exchange.stream.generate: 334.716708 hg.command.bundle: 377.856767 (+12.89%, +43.14) ## data-env-vars.name = mozilla-try-2023-03-22-zstd-sparse-revlog hg.perf.exchange.stream.generate: 302.972301 hg.command.bundle: 326.098755 (+7.63%, +23.13)

     1

=========================================

     2

Testing single head enforcement: Case A-5

     3

=========================================

     4

     5

A repository is set to only accept a single head per name (typically named

     6

branch). However, obsolete changesets can make this enforcement more

     7

complicated, because they can be kept visible by other changeset on other

     8

branch.

     9

    10

This case is part of a series of tests checking this behavior.

    11

    12

Category A: Involving obsolescence

    13

TestCase 5: Obsoleting a merge reveals two heads

    14

    15

.. old-state:

    16

..

    17

.. * 3 changesets on branch default (2 on their own branch + 1 merge)

    18

.. * 1 changeset on branch Z (children of the merge)

    19

..

    20

.. new-state:

    21

..

    22

.. * 2 changesets on branch default (merge is obsolete) each a head

    23

.. * 1 changeset on branch Z keeping the merge visible

    24

..

    25

.. expected-result:

    26

..

    27

.. * 2 heads detected (because we skip the merge)

    28

..

    29

.. graph-summary:

    30

..

    31

..   C ●      (branch Z)

    32

..     |

    33

..   M ⊗

    34

..     |\

    35

..   A ● ● B

    36

..     |/

    37

..     ●

    38

    39

  $ . $TESTDIR/testlib/push-checkheads-util.sh

    40

    41

  $ cat >> $HGRCPATH << EOF

    42

  > [command-templates]

    43

  > log = "{node|short} [{branch}] ({phase}): {desc}\n"

    44

  > EOF

    45

    46

Test setup

    47

----------

    48

    49

  $ mkdir A5

    50

  $ cd A5

    51

  $ setuprepos single-head

    52

  creating basic server and client repo

    53

  updating to branch default

    54

  2 files updated, 0 files merged, 0 files removed, 0 files unresolved

    55

  $ cd client

    56

  $ hg up 0

    57

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    58

  $ mkcommit B0

    59

  created new head

    60

  $ hg merge

    61

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    62

  (branch merge, don't forget to commit)

    63

  $ hg ci -m 'M0'

    64

  $ hg branch Z

    65

  marked working directory as branch Z

    66

  (branches are permanent and global, did you want a bookmark?)

    67

  $ mkcommit C0

    68

  $ hg push --new-branch

    69

  pushing to $TESTTMP/A5/server

    70

  searching for changes

    71

  adding changesets

    72

  adding manifests

    73

  adding file changes

    74

  added 3 changesets with 2 changes to 2 files

    75

  $ hg debugobsolete `getid "desc(M0)"` --record-parents

    76

  1 new obsolescence markers

    77

  obsoleted 1 changesets

    78

  1 new orphan changesets

    79

  $ hg heads

    80

  61c95483cc12 [Z] (draft): C0

    81

  74ff5441d343 [default] (draft): B0

    82

  8aaa48160adc [default] (draft): A0

    83

  $ hg log -G --hidden

    84

  @  61c95483cc12 [Z] (draft): C0

    85

  |

    86

  x    14d3d4d41d1a [default] (draft): M0

    87

  |\

    88

  | o  74ff5441d343 [default] (draft): B0

    89

  | |

    90

  o |  8aaa48160adc [default] (draft): A0

    91

  |/

    92

  o  1e4be0697311 [default] (public): root

    93

    94

    95

Actual testing

    96

--------------

    97

    98

(force push to make sure we get the changeset on the remote)

    99

   100

  $ hg push -r 'desc("C0")' --force

   101

  pushing to $TESTTMP/A5/server

   102

  searching for changes

   103

  no changes found

   104

  transaction abort!

   105

  rollback completed

   106

  abort: rejecting multiple heads on branch "default"

   107

  (2 heads: 8aaa48160adc 74ff5441d343)

   108

  [255]