about
The GitHub Recent Bugs Dataset for Evaluating LLM-Based Debugging Applications (arxiv.org)
2 points by PaulHoule on Oct 27, 2023 | hide | past | pdf | 1 comment on HN

In plain words: Checking an open model's training data, they found the widely used Java bug benchmark was likely already seen, so high debugging scores might just be memorization. To fix this, they collected 76 real Java bugs from GitHub posted after the training data cutoff.

Abstract · The GitHub Recent Bugs Dataset for Evaluating LLM-based Debugging Applications

Large Language Models (LLMs) have demonstrated strong natural language processing and code synthesis capabilities, which has led to their rapid adoption in software engineering applications. However, details about LLM training data are often not made public, which has caused concern as to whether existing bug benchmarks are included. In lieu of the training data for the popular GPT models, we examine the training data of the open-source LLM StarCoder, and find it likely that data from the widely used Defects4J benchmark was included, raising the possibility of its inclusion in GPT training data as well. This makes it difficult to tell how well LLM-based results on Defects4J would generalize, as for any results it would be unclear whether a technique's performance is due to LLM generalization or memorization. To remedy this issue and facilitate continued research on LLM-based SE, we present the GitHub Recent Bugs (GHRB) dataset, which includes 76 real-world Java bugs that were gathered after the OpenAI data cut-off point.

Jae Yong Lee, Sungmin Kang, Juyeon Yoon, Shin Yoo
arXiv:2310.13229 · cs.SE · submitted Oct 20, 2023 · updated Nov 2, 2023
abstract · pdf · html

add comment on HN

I've been surprised that evaluation dataset leakage into training dataset is not discussed more, given that LLM creators often don't reveal their training data