diff options
author | Taylor Blau <me@ttaylorr.com> | 2020-06-01 12:01:31 -0600 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-06-04 07:54:08 -0700 |
commit | 94fbd9149a2d59b0dca18448ef9d3e0607a7a19d (patch) | |
tree | 8d324c66cb6ac9e6b163b18379d352bc357df04b /t/t9161-git-svn-mergeinfo-push.sh | |
parent | t5318: use 'test_must_be_empty' (diff) | |
download | tgif-94fbd9149a2d59b0dca18448ef9d3e0607a7a19d.tar.xz |
t5318: test that '--stdin-commits' respects '--[no-]progress'
The following lines were not covered in a recent line-coverage test
against Git:
builtin/commit-graph.c
5b6653e5 244) progress = start_delayed_progress(
5b6653e5 268) stop_progress(&progress);
These statements are executed when both '--stdin-commits' and
'--progress' are passed. Introduce a trio of tests that exercise various
combinations of these options to ensure that these lines are covered.
More importantly, this is exercising a (somewhat) previously-ignored
feature of '--stdin-commits', which is that it respects '--progress'.
Prior to 5b6653e523 (builtin/commit-graph.c: dereference tags in
builtin, 2020-05-13), dereferencing input from '--stdin-commits' was
done inside of commit-graph.c.
Now that an additional progress meter may be generated from outside of
commit-graph.c, add a corresponding test to make sure that it also
respects '--[no]-progress'.
The other location that generates progress meter output (from d335ce8f24
(commit-graph.c: show progress of finding reachable commits,
2020-05-13)) is already covered by any test that passes '--reachable'.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Acked-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9161-git-svn-mergeinfo-push.sh')
0 files changed, 0 insertions, 0 deletions