git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [Breakage] 2.20.0-rc0 t1404: test_i18ngrep reports 1 instead of 0 on NonStop in one case
Date: Sun, 10 Feb 2019 14:08:30 -0500	[thread overview]
Message-ID: <000801d4c174$05b76860$11263920$@nexbridge.com> (raw)

Hi All,

I tracked down a breakage in t1404 subtest 52. The line

test_i18ngrep "Unable to create $Q.*packed-refs.lock$Q: File exists" err

is correctly working, but is reporting a completion 1.

The verbose output, with diagnostics, is:

error: 'grep Unable to create '.*packed-refs.lock': File exists err' didn't
find a match in:
error: Unable to create '/home/git/git/t/trash
directory.t1404-update-ref-errors/.git/packed-refs.lock': File already
exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.

Reported 1 from test_i18ngrep

err contains (without the double quotes):
"error: Unable to create '/home/git/git/t/trash
directory.t1404-update-ref-errors/.git/packed-refs.lock': File already
exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue."

Which means that 

! test_have_prereq C_LOCALE_OUTPUT || test_cmp "$@"

is completing with a 1. Is that the intent? Any clues?

Thanks,
Randall


             reply	other threads:[~2019-02-10 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10 19:08 Randall S. Becker [this message]
2019-02-11  9:56 ` [Breakage] 2.20.0-rc0 t1404: test_i18ngrep reports 1 instead of 0 on NonStop in one case Duy Nguyen
2019-02-11 14:09   ` Randall S. Becker
2019-02-11 21:07   ` Junio C Hamano
2019-02-11 21:48     ` Randall S. Becker
2019-02-12  0:27     ` Jeff King
2019-02-12  0:32       ` Junio C Hamano
2019-02-12  0:35         ` Jeff King
2019-02-14 20:16       ` Re* " Junio C Hamano
2019-02-14 20:32         ` Randall S. Becker
2019-02-14 21:15           ` Junio C Hamano
2019-02-15  6:08         ` Martin Ågren
2019-02-15 17:51           ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000801d4c174$05b76860$11263920$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).