Live data from Hacker News

Some critical issues with the SWE-bench dataset

arxiv.org

21–30 of 121 posts

Re: Some critical issues with the SWE-bench dataset

#21
> 32.67% of the successful patches involve cheating as the solutions were directly provided in the issue report or the comments.

Looking at the benchmark, https://www.swebench.com/, about half of scored submissions score under 1/3 correct? So they're either not cheating, or not cheating effectively?

Re: Some critical issues with the SWE-bench dataset

#22
post #3

> When we filtered out these problematic issues, the resolution rate of SWE-Agent+GPT-4 dropped from 12.47% to 3.97%. This matches my intuition about the coding performance of these models a lot better. I don't think any current coding benchmark accurately measures coding performance.

o3-mini and gpt-4o are so piss poor in agent coding compared to claude that you don't even need a benchmark

Re: Some critical issues with the SWE-bench dataset

#23
post #7

I am shocked— shocked —when a vendor cheats in order to increase their benchmark scores. I always tell my customers to ignore benchmarks and compare outcomes with their own workloads. Benchmarks are almost completely useless in the real world.

I don't know why you are getting downrated. That is sane advice.

Re: Some critical issues with the SWE-bench dataset

#24
I would argue almost every popular benchmark quoted by the big LLM companies is tainted.

OAI, xAI, Antropic, Google all score incredibly well, then you go to try and write code and its just okay.

They claim it can do PHD level reasoning, but here I am not trusting it on basic computational thinking.

Re: Some critical issues with the SWE-bench dataset

#25
post #22
post #3

> When we filtered out these problematic issues, the resolution rate of SWE-Agent+GPT-4 dropped from 12.47% to 3.97%. This matches my intuition about the coding performance of these models a lot better. I don't think any current coding benchmark accurately measures coding performance.

o3-mini and gpt-4o are so piss poor in agent coding compared to claude that you don't even need a benchmark

o3-mini-medium is slower than claude but comparable in quality. o3-mini-high is even slower, but better.

Re: Some critical issues with the SWE-bench dataset

#26
post #3

> When we filtered out these problematic issues, the resolution rate of SWE-Agent+GPT-4 dropped from 12.47% to 3.97%. This matches my intuition about the coding performance of these models a lot better. I don't think any current coding benchmark accurately measures coding performance.

I personally use Aider's Polyglot Benchmark [0] which is a bit low-key and not gamed just yet. It matches my experience too where Claude Sonnet 3.5 is the best and still beats the new reasoning models like o3-mini, DeepSeek, etc.

0. https://aider.chat/docs/leaderboards/

Re: Some critical issues with the SWE-bench dataset

#27
post #21

> 32.67% of the successful patches involve cheating as the solutions were directly provided in the issue report or the comments. Looking at the benchmark, https://www.swebench.com/ , about half of scored submissions score under 1/3 correct? So they're either not cheating, or not cheating effectively?

yeah, in the abstract they demoted the score from 12% to 3%, so sadly retirement is not yet here :(

Re: Some critical issues with the SWE-bench dataset

#28
post #21

> 32.67% of the successful patches involve cheating as the solutions were directly provided in the issue report or the comments. Looking at the benchmark, https://www.swebench.com/ , about half of scored submissions score under 1/3 correct? So they're either not cheating, or not cheating effectively?

LLMs do not reliably reproduce their training data. This is quite easy to demonstrate, every LLM has been trained on all of wikipedia (at minimum) and yet there if you ask it a niche fact mentioned once on wikipedia it is highly likely to get it wrong.

Re: Some critical issues with the SWE-bench dataset

#29
post #22
post #3

> When we filtered out these problematic issues, the resolution rate of SWE-Agent+GPT-4 dropped from 12.47% to 3.97%. This matches my intuition about the coding performance of these models a lot better. I don't think any current coding benchmark accurately measures coding performance.

o3-mini and gpt-4o are so piss poor in agent coding compared to claude that you don't even need a benchmark

Claude really is a step above the rest when it comes to agentic coding.

Re: Some critical issues with the SWE-bench dataset

#30

I would argue almost every popular benchmark quoted by the big LLM companies is tainted. OAI, xAI, Antropic, Google all score incredibly well, then you go to try and write code and its just okay . They claim it can do PHD level reasoning, but here I am not trusting it on basic computational thinking.

Yeah, that's true in many fields with these AI agents. They demo well, but when you put them to actual work they fall right on their face. Even worse, the harder the task you set for them the more they lie to you. It's like hiring a junior dev from one of those highly regimented societies where it's more important to save face than to get the job done.
Post reply on HN