Oh, my bad. I finally understood my mistake. "git bisect" always
expects you to search for a regression, not the other way round. So
"bad" revisions are supposed to be more recent than "good" revisions.
Regards
Antoine.
Le 26/06/2021 à 17:00, Antoine Pitrou a écrit :
Hello,
I haven't
Hello,
I haven't bisected the Python source tree in a long time and it seems
our current way of making releases is messing it up.
# Start on tip of branch 3.9
(3.9)$ git bisect start
# 3.9 tip is good
(3.9|BISECTING)$ git bisect good
# Switch to release 3.9.1, where the bug wasn't fi
