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

Workflow for bisecting with test in a branch

From
Victor Engmark <victor@engmark.name>
Date
Apr 27, 2025, 08:18 UTC
Message-ID
<02671927-2e65-4bd3-904b-b564849d1fa5@engmark.name>

I'd like to bisect using a test I've written in a different branch from the one I'm bisecting. But to do `git bisect run ./test.bash` I have to keep the new test file and an old test suite file the same during the whole `bisect` process. This turned out pretty cumbersome:

test.bash:

``` #!/usr/bin/env bash

set -o errexit

git show my-test-branch:test-suite-path > test-suite-path mkdir -p test-dir git show my-test-branch:test-dir/test-file > test-dir/test-file

run_test || exit_code=$? git checkout . exit "${exit_code-0}" ```

Console session:

``` git bisect start my-test-branch known-good-ancestor git bisect run ./test.bash ```

Is there a more streamlined way to achieve the same thing, that is, forcing some checked-in files to not change while bisecting?

Kind regards Victor Engmark

Next: Christian Couder
Message 1 of 2 in “Workflow for bisecting with test in a branch”
  1. Victor EngmarkApr 27, 2025
  2. Christian CouderApr 28, 2025

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.