From: Lars Schneider <larsxschneider@gmail.com>
To: Luke Diamand <luke@diamand.org>
Cc: git@vger.kernel.org, sunshine@sunshineco.com, gitster@pobox.com
Subject: Re: [PATCH v5 5/6] git-p4: add trap to kill p4d on test exit
Date: Tue, 17 Nov 2015 09:29:49 +0100 [thread overview]
Message-ID: <8C9A93DB-040E-49FE-B6F7-8373D8CE7601@gmail.com> (raw)
In-Reply-To: <5649974A.1010903@diamand.org>
On 16 Nov 2015, at 09:43, Luke Diamand <luke@diamand.org> wrote:
> On 15/11/15 13:08, larsxschneider@gmail.com wrote:
>> From: Lars Schneider <larsxschneider@gmail.com>
>>
>> Sometimes the "prove" test runner hangs on test exit because p4d is
>> still running. Add a trap to always kill "p4d" on test exit.
>
> With this change, I've started seeing this when running the tests:
>
> cat: /home/lgd/git/git/t/trash directory.t9819-git-p4-case-folding/p4d.pid: No such file or directory
>
> Probably just needs the obvious "test -f" adding.
>
> Other than, all looks good to me. Particularly nice that I can now do:
>
> $ make T=t98* -j10
>
> and it actually works!
Great! I can see where the cat error comes from. I will add the "test -f" condition in the next roll.
Thanks,
Lars
>
>
>
>
>
>>
>> You can reproduce the problem by commenting "P4D_TIMEOUT" in
>> "lib-git-p4.sh" and running "prove ./t9800-git-p4-basic.sh".
>> ---
>> t/lib-git-p4.sh | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/t/lib-git-p4.sh b/t/lib-git-p4.sh
>> index f2a009c..f9c68d4 100644
>> --- a/t/lib-git-p4.sh
>> +++ b/t/lib-git-p4.sh
>> @@ -65,6 +65,12 @@ cli="$TRASH_DIRECTORY/cli"
>> git="$TRASH_DIRECTORY/git"
>> pidfile="$TRASH_DIRECTORY/p4d.pid"
>>
>> +# Sometimes "prove" seems to hang on exit because p4d is still running
>> +cleanup() {
>> + kill -9 $(cat "$pidfile") 2>/dev/null && exit 255
>> +}
>> +trap cleanup EXIT
>> +
>> # git p4 submit generates a temp file, which will
>> # not get cleaned up if the submission fails. Don't
>> # clutter up /tmp on the test machine.
>>
>
next prev parent reply other threads:[~2015-11-17 8:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 13:08 [PATCH v5 0/6] Add Travis CI support larsxschneider
2015-11-15 13:08 ` [PATCH v5 1/6] implement test_might_fail using a refactored test_must_fail larsxschneider
2015-11-15 13:08 ` [PATCH v5 2/6] add "ok=sigpipe" to test_must_fail and use it to fix flaky tests larsxschneider
2015-11-15 13:08 ` [PATCH v5 3/6] git-p4: retry kill/cleanup operations in tests with timeout larsxschneider
2015-11-16 8:36 ` Luke Diamand
2015-11-17 8:22 ` Lars Schneider
2015-11-17 9:38 ` Luke Diamand
2015-11-16 21:14 ` Eric Sunshine
2015-11-17 8:28 ` Lars Schneider
2015-11-17 8:35 ` Eric Sunshine
2015-11-17 9:34 ` Luke Diamand
2015-11-17 17:44 ` Eric Sunshine
2015-11-17 23:40 ` Luke Diamand
2015-11-15 13:08 ` [PATCH v5 4/6] git-p4: add p4d timeout in tests larsxschneider
2015-11-16 8:39 ` Luke Diamand
2015-11-15 13:08 ` [PATCH v5 5/6] git-p4: add trap to kill p4d on test exit larsxschneider
2015-11-16 8:43 ` Luke Diamand
2015-11-17 8:29 ` Lars Schneider [this message]
2015-11-15 13:08 ` [PATCH v5 6/6] Add Travis CI support larsxschneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8C9A93DB-040E-49FE-B6F7-8373D8CE7601@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).