Search with no results returns empty output
Tests ability to handle searches with no results (empty output). Evaluates edge-case handling in search operations.
Baseline Repository
These commands set up the repo before the model sees the prompt. They define the starting file structure, staged changes, and Git history.
- 01
git init - 02
git config user.email 'test@test.com' - 03
git config user.name 'Test User' - 04
echo 'def hello(): return "world"' > hello.py - 05
git add hello.py - 06
git commit -m 'Add hello function' - 07
echo 'git grep nonexistent_token_xyz' > .grep_command - 08
git add .grep_command - 09
git commit -m 'Add grep sentinel'
Prompt
Here is the output of a git grep command run on this repository. Did the search find any matches? Output ONLY 'yes' or 'no', nothing else.
Expected
no
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
no
no
JSON Schema
Structured Output
(raw) { "found": "no" }
no
no
no
JSON Schema
Structured Output
(raw) { "found": "no" }
no
no
JSON Schema
Structured Output
(raw) {
"found": "no"
}
no
no
JSON Schema
Structured Output
(raw) {"found": "no"}
no
yes
Failure: Expected 'no', got 'yes'
yes
JSON Schema
Structured Output
(raw) {
"found": "yes"
}
Failure: Expected 'no', got 'yes'
yes
JSON Schema
Structured Output
(raw) {"found": "yes"}
Failure: Expected 'no', got 'yes'
yes
JSON Schema
Structured Output
(raw) {"found": "yes"}
Failure: Expected 'no', got 'yes'