building working tree doesn't update sha cache
Bug #740932 reported by
John A Meinel
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
The first time you build the working tree, you know that all the files match the basis revision. However, we don't set the sha and mtime values in the dirstate file. The first time you run 'bzr status' or 'bzr commit' will be quite a bit slower, but will end up updating those values.
On my testing with something like GCC, this was about 2min spent re-hashing every file. Which is fairly significant if you are using a new working tree for each feature branch.
Related branches
lp:~jameinel/bzr/2.4-transform-cache-sha-740932
- Andrew Bennetts: Approve
-
Diff: 134 lines (+61/-6)3 files modifiedbzrlib/tests/test_transform.py (+48/-0)
bzrlib/transform.py (+7/-6)
doc/en/release-notes/bzr-2.4.txt (+6/-0)
| tags: | added: dirstate performance |
| tags: | added: affects-linaro |
| Changed in bzr: | |
| assignee: | nobody → John A Meinel (jameinel) |
| Changed in bzr: | |
| status: | Confirmed → In Progress |
| Changed in bzr: | |
| milestone: | none → 2.4b2 |
| status: | In Progress → Fix Released |
To post a comment you must log in.
