Discussion
0 posts
No posts in this thread yet.
benchmarks.wiki / Public workspace
Code
BigCodeBench poses 1,140 function-level tasks drawn across 139 libraries. It tests whether a model can compose several real APIs correctly rather than write one self-contained function.
bigcodebench
Full text: eligible public problems include text, images and discussion.
The BigCode project introduced BigCodeBench in 2024 to evaluate code generation that combines practical library functionality. It addressed a gap left by benchmarks dominated by short, self-contained functions. The dataset distribution recorded in this catalogue was published in June 2024.
BigCodeBench was developed through model-assisted task creation and human review of the resulting programming tasks. It contains 1,140 function-level tasks covering 139 libraries, with reference implementations and executable unit tests. The same tasks have a detailed docstring form and an instruction-style form, and correctness is evaluated by running candidate code against the tests.
Two forms of the same task — a complete docstring prompt and an instruction-style prompt — plus the code skeleton, the entry point, the libraries involved and the structured docstring.
Correctness is decided by running a unittest suite against the candidate, so the reference solution the source ships is not a graded answer; it stays in restricted storage.
Metric: Pass@1 (the official runner also reports Pass@5 and Pass@10)
The libraries have to be used as they actually behave, not as they are usually summarised. Most failures are correct-looking calls with the wrong arguments or the wrong return handling.
Passing the supplied tests establishes agreement with their checks rather than correctness for every possible input. Library versions and the execution environment matter because tasks depend on external APIs. Function-level generation does not directly assess maintaining a large repository or negotiating ambiguous requirements. Results from the docstring and instruction variants should be distinguished, as should single-attempt and multiple-attempt pass rates.
@article{zhuo2024bigcodebench,
title={BigCodeBench: Benchmarking Code Generation with Diverse Function Calls and Complex Instructions},
author={Terry Yue Zhuo and Minh Chien Vu and Jenny Chim and Han Hu and Wenhao Yu and Ratnadira Widyasari and Imam Nur Bani Yusuf and Haolan Zhan and Junda He and Indraneil Paul and Simon Brunner and Chen Gong and Thong Hoang and Armel Randy Zebaze and Xiaoheng Hong and Wen-Ding Li and Jean Kaddour and Ming Xu and Zhihan Zhang and Prateek Yadav and Naman Jain and Alex Gu and Zhoujun Cheng and Jiawei Liu and Qian Liu and Zijian Wang and Binyuan Hui and Niklas Muennighoff and David Lo and Daniel Fried and Xiaoning Du and Harm de Vries and Leandro Von Werra},
journal={arXiv preprint arXiv:2406.15877},
year={2024}
}1 thread and 0 posts on this page. Anyone may reply; no account is required.
Share a reproduction, report an evaluation issue, or suggest a correction to this benchmark overview.
0 posts
No posts in this thread yet.
Whole public benchmark.
Pinned source revisions, newest first:
b74c0d0bf70d2c0bc459be537895cca163007f1a · acquired 2026-09-12 · release 7fd659a6a430b74c0d0bf70d2c0bc459be537895cca163007f1a · acquired 2026-09-12 · release 4ef02375478cb74c0d0bf70d2c0bc459be537895cca163007f1a · acquired 2026-09-12 · release 1b4e12bf295fAnswer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source
Answer published by the source