git bisect run for automated bisect - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to start a git bisect session.

Git

git bisect [1]

Drag options to blanks, or click blank then click option'

Alog

Brun

Creset

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' instead of 'start' to begin bisect.

The command git bisect start begins a bisect session.

2fill in blank

medium

Complete the command to mark a commit as bad in git bisect.

Git

git bisect [1]

Drag options to blanks, or click blank then click option'

Areset

Bbad

Cskip

Dgood

Attempts:

3 left

💡 Hint

Common Mistakes

Marking bad commits as 'good' by mistake.

Use git bisect bad to mark the current commit as bad.

3fill in blank

hard

Fix the error in the command to run an automated test script during bisect.

Git

git bisect [1] ./test_script.sh

Drag options to blanks, or click blank then click option'

Arun

Bstart

Creset

Dlog

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' instead of 'run' to execute the script.

The git bisect run command runs the test script automatically on each commit.

4fill in blank

hard

Fill both blanks to mark the known good and bad commits before running bisect.

Git

git bisect start
git bisect [1]
git bisect [2] <good-commit>

Drag options to blanks, or click blank then click option'

Abad

Bgood

Creset

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of good and bad commits.

Mark the current commit as bad with git bisect bad, then mark the known good commit with git bisect good <good-commit> after starting bisect.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that filters commits by message length and keyword.

Git

filtered = [1]: commit for commit in commits if len(commit.message) [2] 50 and '[3]' in commit.message

Drag options to blanks, or click blank then click option'

Acommit.hash

B<

Cfix

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit object as key instead of commit hash.

This comprehension creates a dict with commit hashes as keys for commits with message length less than 50 and containing 'fix'.

Practice

1. What is the main purpose of git bisect run in debugging?

easy

A. To manually mark commits as good or bad during bisect

B. To automate the process of finding the first bad commit using a test script

C. To reset the repository to the latest commit

D. To merge two branches automatically

Solution

1. Step 1: Understand the role of git bisect run

   This command automates the bisect process by running a test script on each commit to check if it is good or bad.

2. Step 2: Compare with other options

   Manual marking is done without run, resetting or merging are unrelated to bisect automation.

3. Final Answer:

   To automate the process of finding the first bad commit using a test script -> Option B

4. Quick Check:

   Automation with test script = B [OK]

Hint: Remember: git bisect run automates testing commits [OK]

Common Mistakes:

• Confusing manual bisect with automated bisect
• Thinking it resets or merges branches
• Assuming it marks commits without a script

2. Which of the following is the correct syntax to start an automated bisect with a test script named test.sh?

easy

A. git bisect start test.sh

B. git bisect automate test.sh

C. git bisect run ./test.sh

D. git bisect test ./test.sh

Solution

1. Step 1: Recall the correct command structure

   The correct syntax to run a test script during bisect is git bisect run <script>.

2. Step 2: Match options with syntax

   Only git bisect run ./test.sh matches the correct syntax with the script path ./test.sh.

3. Final Answer:

   git bisect run ./test.sh -> Option C

4. Quick Check:

   Correct syntax = D [OK]

Hint: Use git bisect run <script> to automate tests [OK]

Common Mistakes:

• Using 'start' instead of 'run'
• Omitting './' before script name
• Using incorrect verbs like 'automate' or 'test'

3. Given the following test script test.sh that exits with 1 if a file bug.txt exists, else exits 0:

#!/bin/sh
if [ -f bug.txt ]; then
  exit 1
else
  exit 0
fi

What will git bisect run ./test.sh interpret if bug.txt is present in a commit?

medium

A. The commit will be skipped

B. The commit is good

C. The bisect will stop with an error

D. The commit is bad

Solution

1. Step 1: Understand exit codes in test script

   The script exits with 1 if bug.txt exists, which means failure (bad commit).

2. Step 2: Interpret exit code in bisect context

   git bisect run treats exit code 0 as good and non-zero as bad, so exit 1 means bad commit.

3. Final Answer:

   The commit is bad -> Option D

4. Quick Check:

   Exit 1 = bad commit = A [OK]

Hint: Exit 0 means good; non-zero means bad in bisect scripts [OK]

Common Mistakes:

• Confusing exit 1 as good
• Assuming script errors stop bisect
• Thinking bisect skips commits on exit 1

4. You run git bisect run ./test.sh but it stops with the error: ./test.sh: Permission denied. What is the most likely cause?

medium

A. The test script is missing execute permission

B. The bisect command is misspelled

C. The repository is not initialized

D. The test script returns exit code 0

Solution

1. Step 1: Analyze the error message

   The error Permission denied means the shell cannot run the script, often due to missing execute permission.

2. Step 2: Check other options

   Bisect command spelling or repo initialization would cause different errors; exit code 0 does not cause this error.

3. Final Answer:

   The test script is missing execute permission -> Option A

4. Quick Check:

   Missing execute permission = A [OK]

Hint: Make script executable with chmod +x before running [OK]

Common Mistakes:

• Ignoring file permissions
• Assuming bisect command typo
• Thinking exit code causes command not found

5. You want to find the first bad commit that introduced a bug detected by a Python test script check_bug.py. The script returns exit code 0 if no bug and 1 if bug found. Which sequence of commands correctly automates bisecting?

hard

A. git bisect start; git bisect bad <bad_commit>; git bisect good <good_commit>; git bisect run python3 check_bug.py

B. git bisect start; git bisect good; git bisect bad <bad_commit>; git bisect run python3 check_bug.py

C. git bisect start; git bisect bad; git bisect good <good_commit>; git bisect run python3 check_bug.py

D. git bisect start; git bisect good <bad_commit>; git bisect bad <good_commit>; git bisect run python3 check_bug.py

Solution

1. Step 1: Understand bisect start sequence

   You must start bisect, mark a known bad commit first, then a known good commit, then run the test script.

2. Step 2: Match the correct order

   git bisect start; git bisect bad <bad_commit>; git bisect good <good_commit>; git bisect run python3 check_bug.py correctly marks bad commit first, then good commit, then runs the script with Python.

3. Final Answer:

   git bisect start; git bisect bad <bad_commit>; git bisect good <good_commit>; git bisect run python3 check_bug.py -> Option A

4. Quick Check:

   Bad then good then run script = C [OK]

Hint: Always mark bad commit first, then good, then run script [OK]

Common Mistakes:

• Swapping good and bad commit order
• Forgetting to start bisect
• Running script before marking commits