git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: "Jens Krüger" <Jens.Krueger@frm2.tum.de>
Cc: Eric Sunshine <sunshine@sunshineco.us>, Git List <git@vger.kernel.org>
Subject: Re: Test t2028 failes
Date: Tue, 3 Apr 2018 04:16:38 -0400	[thread overview]
Message-ID: <CAPig+cSsTPKoLfcxrgD4+NhXa5AeWynxumo8Zed_PH-q3U163w@mail.gmail.com> (raw)
In-Reply-To: <cdec466c-ecc9-b1d7-c637-04e63552c759@frm2.tum.de>

On Tue, Apr 3, 2018 at 4:01 AM, Jens Krüger <Jens.Krueger@frm2.tum.de> wrote:
> The actual2 file does not exists, if I call the ./t2028-worktree-move.sh
> with the '-v -i' options, only without any option or with '-v' option.

The content of the various files looks correct, and absence of
"actual2" implies that one of the grep's failed, which is very odd
considering that "out" has the expected content.

Using the "out" file you attached, can you show the output of these commands?

    grep "^worktree.*/destination" out
    echo $?
    grep "^worktree.*/source" out
    echo $?

I'd expect the first $? to report 0 and the second 1 in a working installation.

Also, are you using an unusual 'grep'? What does "command -v grep" report?

  reply	other threads:[~2018-04-03  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03  6:33 Test t2028 failes Jens Krüger
2018-04-03  6:58 ` Eric Sunshine
2018-04-03  8:01   ` Jens Krüger
2018-04-03  8:16     ` Eric Sunshine [this message]
2018-04-03  8:38       ` Jens Krüger
2018-04-03  8:45         ` Eric Sunshine
2018-04-03  8:42       ` Jens Krüger
2018-04-03  8:47         ` Eric Sunshine
2018-04-03  8:51           ` Jens Krüger

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=CAPig+cSsTPKoLfcxrgD4+NhXa5AeWynxumo8Zed_PH-q3U163w@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=Jens.Krueger@frm2.tum.de \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.us \
    /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).