comparison tests/test-http.t @ 42897:d7304434390f

changegroup: move message about added changes to transaction summary Before that, applying multiple changegroups in the same transaction issued the message multiple time. This result in a confusing output: adding changesets adding manifests adding file changes added 32768 changesets with 60829 changes to 2668 files adding changesets adding manifests adding file changes added 8192 changesets with 16885 changes to 1553 files adding changesets adding manifests adding file changes added 1020 changesets with 1799 changes to 536 files adding changesets adding manifests ... Instead, we now only issue the message once at the end of the transaction, summing up all added changesets, changes and files. The line is identical, but happens sightly later in the output. There are other suboptimal behavior around issue multiple changegroup (eg: progress bar). We'll cover them later. This impact of lot of test as one would expect, but a two pass check show they are just the order change we expected. To deal with "under the hood" bundle application by internal code, we had to take a slightly hacky move. We could clean that up with a more official way to enter "under the hood" section, however I want to keep this series simple to get it landed. This kind of change have a very high bit rot rate since it impact a lot of test output.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Sun, 08 Sep 2019 09:42:53 +0200
parents 94faa2e84094
children 181ee2118a96
comparison
equal deleted inserted replaced
42896:7e19b640c53e 42897:d7304434390f
336 devel-peer-request: 1013 bytes of data 336 devel-peer-request: 1013 bytes of data
337 devel-peer-request: finished in *.???? seconds (200) (glob) 337 devel-peer-request: finished in *.???? seconds (200) (glob)
338 bundle2-input-bundle: no-transaction 338 bundle2-input-bundle: no-transaction
339 bundle2-input-part: "reply:changegroup" (advisory) (params: 0 advisory) supported 339 bundle2-input-part: "reply:changegroup" (advisory) (params: 0 advisory) supported
340 bundle2-input-part: "output" (advisory) (params: 0 advisory) supported 340 bundle2-input-part: "output" (advisory) (params: 0 advisory) supported
341 bundle2-input-part: total payload size 100 341 bundle2-input-part: total payload size 55
342 remote: adding changesets 342 remote: adding changesets
343 remote: adding manifests 343 remote: adding manifests
344 remote: adding file changes 344 remote: adding file changes
345 bundle2-input-part: "output" (advisory) supported
346 bundle2-input-part: total payload size 45
345 remote: added 1 changesets with 1 changes to 1 files 347 remote: added 1 changesets with 1 changes to 1 files
346 bundle2-input-part: "output" (advisory) supported
347 bundle2-input-bundle: 2 parts total 348 bundle2-input-bundle: 2 parts total
348 preparing listkeys for "phases" 349 preparing listkeys for "phases"
349 sending listkeys command 350 sending listkeys command
350 devel-peer-request: GET http://localhost:$HGPORT2/?cmd=listkeys 351 devel-peer-request: GET http://localhost:$HGPORT2/?cmd=listkeys
351 devel-peer-request: Vary X-HgArg-1,X-HgProto-1 352 devel-peer-request: Vary X-HgArg-1,X-HgProto-1