Skip to content

Add multi-SKIP case to gfi-sweep eval suite - #1062

Open
deepusnath wants to merge 3 commits into
apache:mainfrom
deepusnath:gfi-sweep-multi-skip-case
Open

Add multi-SKIP case to gfi-sweep eval suite#1062
deepusnath wants to merge 3 commits into
apache:mainfrom
deepusnath:gfi-sweep-multi-skip-case

Conversation

@deepusnath

Copy link
Copy Markdown
Contributor

Summary

  • Every existing step-3-present-proposals case in the good-first-issue-sweep eval suite has 0 or 1 SKIP issues, so skip_count_shown_as_summary_only was only ever vacuously satisfied — a model that always returns true would pass.
  • Adds case-5-multi-skip: 1 READY issue plus 6 SKIP issues spread across all three skip_reason categories (2 security-sensitive, 2 architectural-decision, 2 deprecation-decision), so the summary-only rule and the (security: M, architectural: K, deprecation: J) breakdown format from the skill's Step 3 SKIP section actually get exercised.
  • Updates the suite README to document the new case and bump the step-3 case count from 4 to 5.

Closes #1001

Test plan

  • PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/good-first-issue-sweep/step-3-present-proposals/fixtures/ — all 5 cases load and render cleanly (exit 0).
  • Verified expected.json contains all 8 output-spec fields with correct values for the new case.

Pattern 8's eval-suite layout omitted assertions.json, so a reader
following it exactly produces cases with has_*/mention_* expected
keys that silently fall back to MANUAL grading instead of PASS/FAIL.

- Add assertions.json to the fixtures directory-layout block.
- Add a paragraph explaining the has_*/mention_* structural-key rule
  and linking to eval-driven-development.md for the format.

Closes apache#1004
Every existing step-3-present-proposals case has 0 or 1 SKIP issues, so
skip_count_shown_as_summary_only was vacuously satisfied and a model
that always returned true would pass. case-5-multi-skip adds 1 READY
issue plus 6 SKIP issues spread across all three skip_reason categories
(2 security-sensitive, 2 architectural-decision, 2 deprecation-decision)
so the summary-only rule and the (security: M, architectural: K,
deprecation: J) breakdown format actually get exercised.

Closes apache#1001
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a multi-SKIP case so the gfi-sweep summary-only rule can actually fail

1 participant