git bisect run for automated bisect - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of git bisect run with a simple test script

You run git bisect run ./test_script.sh where test_script.sh exits 0 if the commit is good and 1 if bad. What will be the final output after bisect completes?

Git

git bisect start
# Assume bad commit is HEAD, good commit is v1.0
# test_script.sh returns 0 on good, 1 on bad
# git bisect run ./test_script.sh

A

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[commit_hash] Commit message

Bisecting incomplete, manual intervention needed

B

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[commit_hash] Commit message

No bad commits found

C

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[commit_hash] Commit message

<commit_hash> is the first bad commit

D

error: ./test_script.sh: command not found
Bisecting stopped

💡 Hint

Think about what git bisect run does when the test script returns 0 or 1.

git bisect run uses the test script exit code to mark commits as good (0) or bad (1). It automatically finds the first bad commit and outputs it.

🧠 Conceptual

intermediate

Purpose of git bisect run

What is the main purpose of using git bisect run in a git repository?

A To create a new branch and switch to it

B To automatically find the first bad commit by running a test script on each commit

C To merge two branches automatically without conflicts

D To reset the repository to the last commit

💡 Hint

Think about how automation helps in finding bugs in commits.

git bisect run automates the process of running a test script on each commit during bisect to find the first bad commit.

❓ Troubleshoot

advanced

Why does git bisect run stop unexpectedly?

You run git bisect run ./test_script.sh but bisect stops after a few commits with the message: error: test_script.sh: command not found. What is the most likely cause?

A The test script is not executable or not in the PATH during bisect

B The repository has no bad commits

C The git bisect command is deprecated

D The test script returns exit code 0

💡 Hint

Check the permissions and location of the test script.

If the test script is not executable or not found in the current directory or PATH, git bisect run cannot execute it and stops with an error.

🔀 Workflow

advanced

Correct sequence to use git bisect run

What is the correct sequence of commands to use git bisect run to find a bad commit?

A 1,3,2,4

B 3,1,2,4

C 2,1,3,4

D 1,2,3,4

💡 Hint

Start bisect, mark bad, mark good, then run the test script.

You must start bisect, mark the current commit as bad, mark a known good commit, then run the test script to automate bisect.

✅ Best Practice

expert

Best practice for writing a test script for git bisect run

Which of the following is the best practice when writing a test script to use with git bisect run?

A Exit with 0 if the commit is good, 1 if bad, and 125 if the test cannot be run

B Always exit with 0 regardless of test result

C Print the commit hash and exit with 2 on bad commits

D Use interactive prompts to ask the user if the commit is good or bad

💡 Hint

Check git bisect run exit code conventions.

git bisect run expects the test script to exit 0 for good, 1 for bad, and 125 to skip the commit if the test cannot be run.