From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Is t5601 flaky for anybody else?
Date: Tue, 17 Oct 2017 10:10:46 -0700 [thread overview]
Message-ID: <20171017171046.GA48544@google.com> (raw)
In-Reply-To: <xmqq376ipdpx.fsf@gitster.mtv.corp.google.com>
On 10/17, Junio C Hamano wrote:
> I seem to be seeing sporadic errors with this test, and today I got
> annoyed enough to do
>
> cd t && while sh t5601-clone.sh -i -v; do :; done
>
> I saw an error from "cp" saying "plink.exe - text file busy" or
> something like that at around test #45; here is an workaround that
> seems to work (the above loop is spinning without problem for
> several minutes now).
I haven't noticed any issues myself but maybe this has something to do
with my changes to this test in the 'bw/protocol-v1' topic?
>
> t/t5601-clone.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/t/t5601-clone.sh b/t/t5601-clone.sh
> index 9c56f771b6..50e40abb11 100755
> --- a/t/t5601-clone.sh
> +++ b/t/t5601-clone.sh
> @@ -308,6 +308,7 @@ test_expect_success 'clone checking out a tag' '
>
> setup_ssh_wrapper () {
> test_expect_success 'setup ssh wrapper' '
> + rm -f "$TRASH_DIRECTORY/ssh-wrapper$X" &&
> cp "$GIT_BUILD_DIR/t/helper/test-fake-ssh$X" \
> "$TRASH_DIRECTORY/ssh-wrapper$X" &&
> GIT_SSH="$TRASH_DIRECTORY/ssh-wrapper$X" &&
> @@ -318,6 +319,7 @@ setup_ssh_wrapper () {
> }
>
> copy_ssh_wrapper_as () {
> + rm -f "${1%$X}$X" &&
> cp "$TRASH_DIRECTORY/ssh-wrapper$X" "${1%$X}$X" &&
> GIT_SSH="${1%$X}$X" &&
> export GIT_SSH
--
Brandon Williams
next prev parent reply other threads:[~2017-10-17 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:04 Is t5601 flaky for anybody else? Junio C Hamano
2017-10-17 17:10 ` Brandon Williams [this message]
2017-10-17 21:02 ` Re* " Junio C Hamano
2017-10-17 21:08 ` Jeff King
2017-10-22 9:36 ` Kaartic Sivaraam
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=20171017171046.GA48544@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).