On Tue, Apr 30, 2019 at 8:41 PM Jeff King <p...@peff.net> wrote: > > On Tue, Apr 30, 2019 at 02:19:11PM +0300, Aleksey Midenkov wrote: > > > > I gave it about 2000 commits (from v2.20.1 to master on git.git) to > > > rebase. No luck. > > > > Please, try on this repo: g...@github.com:tempesta-tech/mariadb > > > > ``` > > git checkout 62a082f573 > > git rebase -p -x /tmp/check.sh ca7fbcea6c4 > > ``` > > It doesn't reproduce for me. > > Usually when we see racy contention on index.lock, the culprit turns out > to be another unrelated git process refreshing the index. Do you have > anything else running which might be using "git status" (e.g., magit in > emacs, vim git integration, etc)? >
kdevelop which is git-aware. But if git fails on concurrent operation this is still not good. I would expect it to wait until lock releases for some time. I confirm, without kdevelop running it doesn't reproduce. > -Peff -- All the best, Aleksey Midenkov @midenok
