buildinspace / peru

93%

master: 88%

LAST BUILD ON BRANCH staleindex

branch: staleindex

CHANGE BRANCH

x

Reset

• staleindex
• 0.1.1
• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.2.4
• 0.2.5
• 0.2.6
• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.4.0
• 1.0.0
• 1.0.1
• 1.1.0
• 1.1.1
• 1.1.2
• 1.1.3
• 1.1.4
• 1.2.0
• appveyor
• appveyor-fix
• appveyor2
• appveyor_clean
• ascii
• cacherewrite
• coalesce
• colon
• delete
• deprecations
• dotgit
• example_fix
• fix
• flags
• github_ci
• list
• master
• omitdotperu
• python39
• recursiondefault
• searchname
• testingbadge
• third_party
• travis_python3.9
• treeops
• uncomment
• windows

Build # 484

Build Type

push

travis-ci

Committed by oconnor663

Commit Message

always update the index file on the slow path

There's a case I'd missed when I wrote the current fast-path-optimized
version of Cache.export(). If a file has been touched, but not actually
changed, it will show up as modified in the first call to diff-files.
That kicks us down the slow path. However, the slow path doesn't
actually call update-index, so the second call to diff-files (which
filters out deletions) *also* shows it as modified, which makes peru
think the working copy is dirty and error out.

Fix this issue by guaranteeing that the slow path will call
update-index, if it wasn't called before.

Run Details

1580 of 1692 relevant lines covered (93.38%)

2.8 hits per line