git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Using --term-* with bisect breaks skip

From
Trygve Aaberge <trygveaa@gmail.com>
Date
Apr 18, 2021, 15:14 UTC
Message-ID
<20210418151459.GC10839@aaberge.net>
What did you do before the bug happened? (Steps to reproduce your issue)
1. git bisect start --term-new=fixed --term-old=unfixed master HEAD~10
2. git bisect skip

What did you expect to happen? (Expected behavior) Git should mark the commit as skipped and change HEAD to a different commit.

What happened instead? (Actual behavior) The commit was marked as skipped, but HEAD was not changed.

What's different between what you expected and what actually happened? After running bisect skip, HEAD was still at the same commit as before, instead of having changed to a new that I can test. The usual output about steps left to test and the new commit was also missing, skip did not output anything.

Anything else you want to add:
- If I don't provide any --term-* options, skip works as expected.
- The revisions provided in the reproduction steps doesn't matter, they're
  just an example.
- I tried running from the next branch, and it happened there too.

[System Info] git version: git version 2.31.1 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 5.10.29-1-lts #1 SMP Sat, 10 Apr 2021 14:40:41 +0000 x86_64 compiler info: gnuc: 10.2 libc info: glibc: 2.33 $SHELL (typically, interactive shell): /usr/bin/zsh

[Enabled Hooks]
-- 
Trygve Aaberge
Next: Bagas Sanjaya
Message 1 of 11 in “Using --term-* with bisect breaks skip”
  1. Trygve AabergeApr 18, 2021
  2. Bagas SanjayaApr 19, 2021
  3. Trygve AabergeApr 19, 2021
  4. Bagas SanjayaApr 19, 2021
  5. Junio C HamanoApr 19, 2021
  6. Trygve AabergeApr 19, 2021
  7. test: add test for git bisect skip with --term* argumentsBagas Sanjaya, Apr 20, 2021
  8. Junio C HamanoApr 20, 2021
  9. test: add test for git bisect skip with --term* argumentsBagas Sanjaya, Apr 21, 2021
  10. Junio C HamanoApr 21, 2021
  11. Bagas SanjayaApr 22, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.