feat: expand benchmark coverage and add BFCL v4 - #1
Merged
Conversation
|
✅ Benchmark documentation has been automatically updated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BFCL naming
bfcl_v4_multi_turnuses the pinned official BFCL state/response checker. The agentic environment is deliberately exposed asbfcl_v4_agentic_offline, and the weighted aggregate asbfcl_v4_offline, because frozen evidence is reproducible but not numerically identical to the live SERPAPI leaderboard environment. No ambiguousbfcl_v4alias is introduced.Validation
pytest -m "not integration and not docker"— 444 passed, 2 skippedpytest -m docker -v tests/integration/test_docker_sandboxes.py— 3 passedmypy .— 466 source files cleanpre-commit run --all-files— all hooks passeduv build --quiet— wheel and sdist builtLimitations
Real-model transport checks across two providers could not be run locally because no provider credentials or local model runtime were available. The provider-neutral paths and mock transport are covered, and the tasks are ready for credentialed CI/manual evaluation.