Datasets:

---

nebius

/

SWE-rebench

like 6

Follow

Nebius 96

@lycfight This is a new, extended dataset built by enhancing the SWE-bench-extra data pipelines.
An official release with full details is coming soon — stay tuned!

@lycfight This is a new, extended dataset built by enhancing the SWE-bench-extra data pipelines.
An official release with full details is coming soon — stay tuned!

I previously attempted to extend the dataset as well, but ran into some difficulties when configuring the environment in the constants file. The official SWE-bench documentation does not clearly explain the details.

In our previous discussion under nebius/SWE-bench-extra, we talked about the limitations of using a single default constants configuration—for many repositories, the default setup fails, and as a result, only a small portion of the instances pass validation. The loss rate is high, and we ended up with only 10–20% usable data after filtering.

You managed to collect 21.3k instances, which is really impressive. Could you share how you efficiently collected them—especially how you handled the constants environment configuration part?

Hi!
Yes, that's true — the default configuration for installation has its limitations. In the current version, we used an automatic installation pipeline, so each task now has its own installation recipe (see the install_config column). These constants are no longer hardcoded, but stored directly inside each task.
You can read more details about the collection process in our tech report.

Hi nebius team, thanks for the awesome work! Want to follow up and wondering do we have any updates for releasing the docker images for both swe-rebench and swe-bench-extra so we can do some eval and training based on this?

Thanks so much!

Hi! Thank you for your kind words!
You can already use the SWE-bench fork to build the images yourself. We’re also planning to publish the Docker images to a public registry in the upcoming release — so stay tuned!

Thanks again for your interest!