When running the test suite for git-1.6.3.3, the process hangs during the test group in t7502-commit.sh. The failing test is #18 in that file, which checks that a SIGTERM during a commit will break the locks. However, the test never completes. Reproducible: Always Steps to Reproduce: 1. FEATURES="test" emerge git Actual Results: Test suite runs up through t7502-commit.sh test #17 ("Editor does not fire in the presence of conflicts"), then emerge process freezes. Expected Results: Test suite should continue to completion and allow git to emerge. Once the process freezes, the ps output includes the following items: portage 10661 0.0 0.1 6752 2048 pts/0 S+ Jul21 0:00 /bin/sh t7502-commit.sh portage 10872 0.0 0.1 6464 2380 pts/0 S+ Jul21 0:00 git commit -a portage 10873 0.0 0.0 0 0 pts/0 Z+ Jul21 0:00 [FAKE_EDITOR] <defunct> By sending a SIGKILL to the `git commit` process, the test continues and fails with the following messages: * FAIL 18: a SIGTERM should break locks echo >>negative && ! "$SHELL_PATH" -c ' echo kill -TERM $$ >> .git/FAKE_EDITOR GIT_EDITOR=.git/FAKE_EDITOR export GIT_EDITOR exec git commit -a' && test ! -f .git/index.lock The contents of the FAKE_EDITOR file is: #! /bin/sh # kill -TERM command added below. kill -TERM 10872
Please retest with 1.6.3.4 and 1.6.4.
I see the exact same behavior in 1.6.4
I still can't reproduce this at all on my machines. Can you provide more information about your set? Your info here suggests that the GIT_EDITOR setting is not being respected, and that another edit is maybe being fired up.
No response from user.
