From: Alexey Kuznetsov <kuznetsov.alexey@gmail.com>
To: git@vger.kernel.org
Subject: git bisect bugs
Date: Tue, 2 Nov 2021 17:15:58 +0300 [thread overview]
Message-ID: <163b01f2-ddc0-c551-5462-e8f80fb7cc48@gmail.com> (raw)
Two 'git bisect' bugs.
1) First git-bisect asks twice for the same commit
219d54332a09e8d8741c1e1982f5eae56099de85.
axet@axet-laptop:/media/axet/1TB/local/linux$ git bisect log
git bisect start
# good: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4
git bisect good 219d54332a09e8d8741c1e1982f5eae56099de85
# bad: [841fca5a32cccd7d0123c0271f4350161ada5507] Linux 5.10.1
git bisect bad f12366d9f172c4fc84cd114801b87588cb663074
# good: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4
git bisect good 219d54332a09e8d8741c1e1982f5eae56099de85
# good: [bce159d734091fe31340976081577333f52a85e4] Merge tag
'for-5.8/drivers-2020-06-01' of git://git.kernel.dk/linux-block
<http://git.kernel.dk/linux-block>
git bisect good bce159d734091fe31340976081577333f52a85e4
# bad: [fbc1ac9d09d70859eee24131d667e01e3986e368] tools/cgroup: add
memcg_slabinfo.py tool
git bisect bad fbc1ac9d09d70859eee24131d667e01e3986e368
axet@axet-laptop:/media/axet/1TB/local/linux$
I expect git bisect did not ask twice for the same commit.
2) Second:
If you start 'git bisect' on "good refs/tags/v5.4.19" and "bad
refs/tags/v5.10.1" it will failed on second step (bad) with following:
Bisecting: a merge base must be tested
then on third step with 'git bisect good' it will result:
"was both good and bad"
I expected 'git bisect' will handle all "connection" issues between two
kernel tags, but it failed.
admin@m3n:~/local/linux$ git bisect bad refs/tags/v5.10.1
Bisecting: a merge base must be tested
[219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4
admin@m3n:~/local/linux$ git bisect good
f12366d9f172c4fc84cd114801b87588cb663074 was both good and bad
bisect log:
git bisect start
# good: [d6591ea2dd1a44b1c72c5a3e3b6555d7585acdae] Linux 5.4.19
git bisect good 1670517c4dcbe1143fd86d8a9eae272d0c514415
# bad: [841fca5a32cccd7d0123c0271f4350161ada5507] Linux 5.10.1
git bisect bad f12366d9f172c4fc84cd114801b87588cb663074
# good: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4
git bisect good 219d54332a09e8d8741c1e1982f5eae56099de85
[System Info]
git version:
git version 2.30.2
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64
compiler info: gnuc: 10.2
libc info: glibc: 2.31
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
-- AK
reply other threads:[~2021-11-02 14:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=163b01f2-ddc0-c551-5462-e8f80fb7cc48@gmail.com \
--to=kuznetsov.alexey@gmail.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).