git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filippo Valsorda <valsorda@google.com>
To: git@vger.kernel.org
Subject: Re: BUG: commit-reach.c:66: bad generation skip
Date: Sun, 7 Feb 2021 23:31:58 +0100	[thread overview]
Message-ID: <CA+2K_KqH=Gn=Yx-UYzMBO+gZje3G3PJ_3-5HeO81wyZKvVwOSA@mail.gmail.com> (raw)
In-Reply-To: <CA+2K_KotVrV=rjE6fcd_FfxxS0sewkywvO0EMVZdoHbSiqJTQw@mail.gmail.com>

I was able to workaround this bug with a "git gc" invocation.

On Sun, Feb 7, 2021 at 11:28 PM Filippo Valsorda <valsorda@google.com> wrote:
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> $ git merge origin/master
>
>
> What happened instead? (Actual behavior)
>
> BUG: commit-reach.c:66: bad generation skip     ad18 >        7 at
> be28e5abc5ddca0d6b2d8c91b7bb9c05717154e7
>
>
> Anything else you want to add:
>
> Running in a worktree of a clone of https://go.googlesource.com/go.
> HEAD is 0d34d85dee216b62a4212d25de57e1119c1e7ee5, branch is
> filippo/boringcrypto/16,
> tracking and matching origin/dev.boringcrypto.
> origin/master is 724d0720b3e110f64598bf789cbe2a6a1b3b0fd8.
>
>
> [System Info]
> git version:
> git version 2.30.0
> cpu: x86_64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Darwin 20.3.0 Darwin Kernel Version 20.3.0: Mon Dec  7 22:04:02
> PST 2020; root:xnu-7195.80.16.111.1~1/RELEASE_X86_64 x86_64
> compiler info: clang: 12.0.0 (clang-1200.0.32.28)
> libc info: no libc information available
> $SHELL (typically, interactive shell): /Users/valsorda/homebrew/bin/zsh
>
>
> [Enabled Hooks]
> pre-commit
> commit-msg

  reply	other threads:[~2021-02-07 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 22:28 BUG: commit-reach.c:66: bad generation skip Filippo Valsorda
2021-02-07 22:31 ` Filippo Valsorda [this message]
2021-02-08  2:26   ` Derrick Stolee
2021-02-10 12:18     ` Filippo Valsorda
2021-02-10 12:24       ` Derrick Stolee
2021-02-10 20:14         ` 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

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

  git send-email \
    --in-reply-to='CA+2K_KqH=Gn=Yx-UYzMBO+gZje3G3PJ_3-5HeO81wyZKvVwOSA@mail.gmail.com' \
    --to=valsorda@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. 
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).