Page MenuHomeSoftware Heritage

Don't update Mercurial repositories after cloning
ClosedPublic

Authored by Alphare on Feb 25 2021, 12:00 PM.

Details

Summary

By default, Mercurial updates to the default revision after cloning,
which - while probably good UX - is wasteful in the context of automated
archival and server-side operations.

Diff Detail

Repository
rDLDHG Mercurial loader
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Build has FAILED

Patch application report for D5141 (id=18382)

Rebasing onto d8572187e9...

First, rewinding head to replay your work on top of it...
Applying: Don't update Mercurial repositories after cloning
Changes applied before test
commit bcecc967a5a2938dc88ef00aff84e4b63ef3e318
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Thu Feb 25 11:54:36 2021 +0100

    Don't update Mercurial repositories after cloning
    
    By default, Mercurial updates to the default revision after cloning,
    which - while probably good UX - is wasteful in the context of automated
    archival and server-side operations.

Link to build: https://jenkins.softwareheritage.org/job/DLDHG/job/tests-on-diff/163/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDHG/job/tests-on-diff/163/console

Harbormaster returned this revision to the author for changes because remote builds failed.Feb 25 2021, 12:01 PM
Harbormaster failed remote builds in B19460: Diff 18382!

Build is green

Patch application report for D5141 (id=18385)

Rebasing onto d8572187e9...

First, rewinding head to replay your work on top of it...
Applying: Don't update Mercurial repositories after cloning
Changes applied before test
commit 800e5378bfa101f61af83c5dcb3b825fd89ea680
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Thu Feb 25 11:54:36 2021 +0100

    Don't update Mercurial repositories after cloning
    
    By default, Mercurial updates to the default revision after cloning,
    which - while probably good UX - is wasteful in the context of automated
    archival and server-side operations.

See https://jenkins.softwareheritage.org/job/DLDHG/job/tests-on-diff/164/ for more details.

ardumont added a subscriber: ardumont.

lgtm

please note the remarks on missing copyright headers

swh/loader/mercurial/tests/test_hgutil.py
1

-2021

Please also update and add the copyright header where missing (in the files you are touching).

This revision is now accepted and ready to land.Feb 25 2021, 12:29 PM

Build is green

Patch application report for D5141 (id=18407)

Rebasing onto d8572187e9...

First, rewinding head to replay your work on top of it...
Applying: Don't update Mercurial repositories after cloning
Changes applied before test
commit 4be2253ff3b5c6e30c9480e9747f3dd92dc39f58
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Thu Feb 25 11:54:36 2021 +0100

    Don't update Mercurial repositories after cloning
    
    By default, Mercurial updates to the default revision after cloning,
    which - while probably good UX - is wasteful in the context of automated
    archival and server-side operations.

See https://jenkins.softwareheritage.org/job/DLDHG/job/tests-on-diff/166/ for more details.

Build is green

Patch application report for D5141 (id=18428)

Rebasing onto d8572187e9...

Current branch diff-target is up to date.
Changes applied before test
commit 1dbb8474ad0a1a6e7cc8d52fcb487bd8a37659c6
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Thu Feb 25 11:54:36 2021 +0100

    Don't update Mercurial repositories after cloning
    
    By default, Mercurial updates to the default revision after cloning,
    which - while probably good UX - is wasteful in the context of automated
    archival and server-side operations.

See https://jenkins.softwareheritage.org/job/DLDHG/job/tests-on-diff/171/ for more details.