[darcs-users] performance regression in check/repair

Trent W. Buck twb at cybersource.com.au
Mon Jan 18 01:59:22 UTC 2010


Jason Dagit <dagit at codersbase.com> writes:

> bindisttest/a/b
>     index: 0000000000000000000000000000000000000000000000000000000000000000
>   working: 5847c8b50a3191775d91cbaf8029fd1a75725517b0c70dde5bff759fc67ec1f8

This is a known problem.  I can't remember where it is in the BTS, but
we were talking about it on #darcs.  Here's the minimal test:

    $ with-temp-dir
    with-temp-dir: entering directory `/tmp/with-temp-dir.erbWhS'
    This directory will be deleted when you exit.
    $ darcs init
    $ mkdir d
    $ darcs rec -qlamd
    Finished recording patch 'd'
    $ darcs check
    The repository is consistent!
    Hash mismatch(es)!
    d
        index: 0000000000000000000000000000000000000000000000000000000000000000
      working: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

    Bad index.
    $ exit
    with-temp-dir: leaving directory `/tmp/with-temp-dir.erbWhS'

I'm using hashed-storage-0.4.4 and Darcs 2.3.1 (+ 426 patches).



More information about the darcs-users mailing list