From: Robbie Iannucci <iannucci@google.com>
To: git@vger.kernel.org
Subject: [BUG] Index.lock error message regression in git 2.11.0
Date: Fri, 2 Dec 2016 17:44:33 -0800 [thread overview]
Message-ID: <CA+q_oBdHytoeSD-hmLx_N473M8XinjqckvE35Re3eNpQRWYjHQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Hello,
I just upgraded to 2.11.0 from 2.10.2, and I noticed that some
commands no longer print an error message when the `index.lock` file
exists (such as `git merge --ff-only`).
It appears this bug was introduced in
55f5704da69d3e6836620f01bee0093ad5e331e8 (sequencer: lib'ify
checkout_fast_forward()). I determined this by running the attached
bisect script (on OS X, but I don't think that matters; I've also seen
the error message missing on Linux):
$ cd /path/to/git/src
$ git bisect start v2.11.0-rc0 v2.10.2
$ git bisect run /path/to/bisect.test.sh
(my original version of the script also includes some other makefile
parameters to get a modern version of gettext and openssl too, but
they're not relevant to this ML).
I'm not certain that I have enough context to propose a meaningful
patch though :/.
Cheers,
Robbie
[-- Attachment #2: bisect.test.sh --]
[-- Type: application/octet-stream, Size: 527 bytes --]
#!/bin/bash
make -j 8 2>&1 > /dev/null
if [[ $? != 0 ]]; then
# skip this version
exit 125
fi
git=`realpath ./git`
rm -rf .test_repo || true
mkdir .test_repo
cd .test_repo
$git init
echo HELLO > a
$git add a
$git commit -m 'initial_commit'
$git branch --track new_branch
$git checkout master
echo HELLO >> a
$git add a
$git commit -m 'second_commit'
$git checkout new_branch
touch .git/index.lock
if $git merge --ff-only master 2>&1 | grep -F "index.lock" ; then
echo OK
exit 0
fi
echo Message is missing
exit 1
next reply other threads:[~2016-12-03 1:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 1:44 Robbie Iannucci [this message]
2016-12-03 1:52 ` [BUG] Index.lock error message regression in git 2.11.0 Robbie Iannucci
2016-12-06 21:56 ` Junio C Hamano
2016-12-06 22:15 ` Re* " Junio C Hamano
2016-12-07 18:21 ` Junio C Hamano
2016-12-07 19:41 ` [PATCH 0/3] Do not be totally silent upon lock error Junio C Hamano
2016-12-07 19:41 ` [PATCH 1/3] wt-status: implement opportunisitc index update correctly Junio C Hamano
2016-12-07 20:48 ` Stefan Beller
2016-12-07 20:53 ` Junio C Hamano
2016-12-07 20:56 ` Stefan Beller
2016-12-07 21:08 ` Junio C Hamano
2016-12-07 22:06 ` Stefan Beller
2016-12-08 10:18 ` Paul Tan
2016-12-08 18:01 ` Junio C Hamano
2016-12-07 19:41 ` [PATCH 2/3] hold_locked_index(): align error handling with hold_lockfile_for_update() Junio C Hamano
2016-12-07 19:41 ` [PATCH 3/3] lockfile: LOCK_REPORT_ON_ERROR Junio C Hamano
2016-12-08 11:53 ` Johannes Schindelin
2016-12-08 18:10 ` Robbie Iannucci
2016-12-08 18:22 ` 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=CA+q_oBdHytoeSD-hmLx_N473M8XinjqckvE35Re3eNpQRWYjHQ@mail.gmail.com \
--to=iannucci@google.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).