Skip to content

[Benchmark] Add BFCL-v4#934

Merged
Yunnglin merged 8 commits intomainfrom
update/bfcl
Oct 30, 2025
Merged

[Benchmark] Add BFCL-v4#934
Yunnglin merged 8 commits intomainfrom
update/bfcl

Conversation

@Yunnglin
Copy link
Collaborator

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Yunnglin, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades the evaluation framework by integrating the Berkeley Function Calling Leaderboard v4 (BFCL-v4). This new benchmark provides a more comprehensive assessment of Large Language Models' function calling abilities, featuring expanded test categories and refined scoring mechanisms. The changes also involve updating dependencies, refactoring the existing BFCL-v3 implementation for better modularity, and enhancing documentation to guide users through the new evaluation process.

Highlights

  • BFCL-v4 Benchmark Integration: The Berkeley Function Calling Leaderboard v4 (BFCL-v4) benchmark has been introduced, significantly expanding the evaluation capabilities for Large Language Models' function calling abilities.
  • BFCL-v3 Refactoring and Updates: The existing BFCL-v3 adapter and related generation logic have been refactored and moved into a dedicated 'v3' subdirectory. The 'bfcl-eval' package version dependency has been updated across documentation and code to '2025.10.27.1'.
  • Enhanced Scoring and Aggregation: BFCL-v4 introduces new, more granular scoring categories (e.g., 'NON_LIVE', 'LIVE', 'MULTI_TURN', 'AGENTIC') and a sophisticated aggregation methodology, including a new 'percentage_weighted_average_from_subsets' utility for more nuanced reporting.
  • Documentation and Test Coverage: Both English and Chinese documentation have been updated to reflect the new 'bfcl-eval' version and revised sample outputs. New test cases specifically for BFCL-v4 have also been added to ensure proper functionality.
  • Utility Improvements: New utility functions have been added to standardize language and format names between BFCL v3 and v4. Additionally, file logging has been updated to explicitly use UTF-8 encoding for better compatibility.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/ci_test_full.yaml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces support for the BFCL-v4 benchmark and refactors the existing BFCL-v3 implementation. A new adapter for v4 is added, along with necessary utility functions and updates to documentation. The v3 adapter is updated for compatibility with the new evaluation flow. The changes are well-structured. My feedback focuses on improving code style by moving local imports to the top of files for better readability and maintainability, and some minor optimizations and maintainability improvements in the new bfcl_v4_adapter.

@Yunnglin
Copy link
Collaborator Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces the BFCL-v4 benchmark, a significant enhancement for evaluating agentic and function-calling capabilities of LLMs. The changes are extensive, including new adapters, utility functions, and comprehensive documentation for both English and Chinese. The existing BFCL-v3 benchmark is also refactored to align with the new evaluation logic, and several core components like caching and logging are improved for better robustness and user experience. My review focuses on improving maintainability, the robustness of the caching mechanism, and the clarity of the documentation.

@Yunnglin Yunnglin merged commit d776d66 into main Oct 30, 2025
3 checks passed
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