Skip to content

Harden robustness boundary evidence - #180

Closed
Anionix wants to merge 1 commit into
mainfrom
codex/robustness-review-contract-fixes
Closed

Anionix wants to merge 1 commit into
mainfrom
codex/robustness-review-contract-fixes

Conversation

@Anionix

@Anionix Anionix commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • preserve HARNESS_FAILED for unexpected verifier exceptions while retaining VALUE_MISMATCH for known comparison ValueError failures
  • record zero cardinality for generated empty cases
  • pass an absolute corpus directory to native libFuzzer targets
  • bound deeply nested worker details and add timeout/output regression coverage

Evidence

Scope

Fresh branch from origin/main; no benchmark results or public manifest data changed.

@Anionix
Anionix force-pushed the codex/robustness-review-contract-fixes branch from 2390e86 to e45f3bf Compare July 16, 2026 18:31

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2390e868df

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/format_bench/robustness/native.py Resolved
@Anionix
Anionix force-pushed the codex/robustness-review-contract-fixes branch from e45f3bf to 6455ec6 Compare July 16, 2026 18:37
@Anionix

Anionix commented Jul 16, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #181 and #183 after #181 merged. #183 carries the non-native contract fixes and validates the merged native corpus_records during release packaging.

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.

1 participant