mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <>
To: "'Git Mailing List'" <>
Subject: [Breakage] 2.22.0-rc1
Date: Tue, 21 May 2019 17:47:54 -0400	[thread overview]
Message-ID: <001501d5101e$db98dfb0$92ca9f10$> (raw)

Another situation came up during regression testing on NonStop:

t5401 broke on the first run through (most tests), with the failures below. 

*** ***
not ok 1 - setup
#               echo This is a test. >a &&
#               git update-index --add a &&
#               tree0=$(git write-tree) &&
#               commit0=$(echo setup | git commit-tree $tree0) &&
#               echo We hope it works. >a &&
#               git update-index a &&
#               tree1=$(git write-tree) &&
#               commit1=$(echo modify | git commit-tree $tree1 -p $commit0)
#               git update-ref refs/heads/master $commit0 &&
#               git update-ref refs/heads/tofail $commit1 &&
#               git clone --bare ./. victim.git &&
#               GIT_DIR=victim.git git update-ref refs/heads/tofail $commit1
#               git update-ref refs/heads/master $commit1 &&
#               git update-ref refs/heads/tofail $commit0
# line 26: victim.git/hooks/pre-receive: No such file
or di
chmod: cannot access 'victim.git/hooks/pre-receive': No such file or
directory line 35: victim.git/hooks/update: No such file or
chmod: cannot access 'victim.git/hooks/update': No such file or directory line 45: victim.git/hooks/post-receive: No such file
or d
chmod: cannot access 'victim.git/hooks/post-receive': No such file or
directory line 54: victim.git/hooks/post-update: No such file
or di
chmod: cannot access 'victim.git/hooks/post-update': No such file or
ok 2 - push

When running the test in isolation, it passes without incident whether or
not --verbose is used. So far, this only occurs on the first run through. I
wanted to report it, based on the inconsistency of results. This is not the
first time tests have acted in this fashion, and I realize it is difficult
to do anything about it without being able to recreate the situation.

Such as it is,

             reply	other threads:[~2019-05-21 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 21:47 Randall S. Becker [this message]
2019-05-22  0:48 ` [Breakage] 2.22.0-rc1 brian m. carlson
2019-05-22 13:46   ` Randall S. Becker
2019-05-23 20:05     ` Issues with t7519.19, was " Johannes Schindelin
2019-05-23 20:18       ` Randall S. Becker
2019-05-23 20:55         ` Johannes Schindelin
2019-05-23 19:57   ` Randall S. Becker
2019-05-23 21:00     ` Johannes Schindelin

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:

  List information:

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

  git send-email \
    --in-reply-to='001501d5101e$db98dfb0$92ca9f10$' \ \ \

* 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

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).