On Fri, May 13, 2016 at 03:25:58PM +0200, Johannes Schindelin wrote: > This patch makes perf-lib.sh more robust so that it can run correctly > even inside a worktree. For example, it assumed that $GIT_DIR/objects is > the objects directory (which is not the case for worktrees) and it used > the commondir file verbatim, even if it contained a relative path. > > Furthermore, the setup code expected `git rev-parse --git-dir` to spit > out a relative path, which is also not true for worktrees. Let's just > change the code to accept both relative and absolute paths, by avoiding > the `cd` into the copied working directory. I was trying to run the perf scripts today and got bit by this patch. The problem is this line: > + objects_dir="$(git -C "$source" rev-parse --git-path objects)" When the perf script is running, the "git" in its PATH is the version of git being perf-tested, not the most recent one. And --git-path wasn't introduced until v2.5.0. So if you try to compare results against an older git, it fails: $ cd t/perf $ ./run v2.4.0 v2.9.0 -- p0000-perf-lib-sanity.sh [...] === Running 1 tests in build/67308bd628c6235dbc1bad60c9ad1f2d27d576cc/bin-wrappers === fatal: ambiguous argument 'objects': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' cp: unrecognized option '--git-path objects' Try 'cp --help' for more information. error: failed to copy repository '/home/peff/compile/git/t/..' to '/var/ram/git-tests/trash directory.p0000-perf-lib-sanity' [...] Test v2.4.0 v2.9.0 -------------------------------------------------------------------------------------- 0000.1: test_perf_default_repo works <missing> 0.00(0.00+0.00) 0000.2: test_checkout_worktree works <missing> 0.01(0.00+0.00) 0000.4: export a weird var <missing> 0.00(0.00+0.00) 0000.6: important variables available in subshells <missing> 0.00(0.00+0.00) 0000.7: test-lib-functions correctly loaded in subshells <missing> 0.00(0.00+0.00) I know that running modern perf tests against older versions isn't guaranteed to work (the tests might rely on newer options, for example), but it at least generally worked up until this point. IMHO the problem is in the design of t/perf, though. It should always use your modern git for the harness setup, and only use the git-to-test inside test_expect and test_perf blocks. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html