[caitlon]

Problem

The guard in AssistantService.answer() that lets a TimeoutError other than the turn's own deadline propagate had no test: deleting it left the suite green.

test_three_failures_in_a_row_stop_the_run_with_exit_3 failed now and then. The runner records git describe --dirty of the live tree as each row's code version, and the test spent a real minute in the pacer between its second and third run. A commit or a first edit in that minute changed the version, so the third run was refused as a provenance change.

Change

• A unit test where the answer model raises a foreign TimeoutError during generation and answer() passes it through.
• The three-run eval test and the test that checks the recorded code version pin git_version, and the three-run test passes --no-pacing, which takes it from about 61 s to under a second.

Verification

• With the guard in answer() removed, the new unit test is the only test in its file that fails.
• The flaky failure was reproduced in a scratch clone by editing a file 20 s into the test; it fails at the third run's summary, as the original failure did.
• ./scripts/ci/ci-local.sh fast.

Migrations

None.

Screenshots

None.

[greptile-apps]

Automatic reviews are disabled for this repository.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud