Yashp2003 commited on
Commit
d26eefd
·
verified ·
1 Parent(s): 1b84f4c

Update logbook: Reproduction: SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks?

Browse files
Files changed (2) hide show
  1. logbook.json +3 -3
  2. pages/deep-verification/page.md +17 -0
logbook.json CHANGED
@@ -8,7 +8,7 @@
8
  "icml2026-repro",
9
  "paper-uEVTdoAbnK"
10
  ],
11
- "updated_at": "2026-07-19T13:02:33+00:00",
12
  "root": {
13
  "slug": "index",
14
  "title": "Reproduction: SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks?",
@@ -70,6 +70,6 @@
70
  }
71
  ]
72
  },
73
- "agent_view_tokens": 9556,
74
- "revision": "1784466153386688257"
75
  }
 
8
  "icml2026-repro",
9
  "paper-uEVTdoAbnK"
10
  ],
11
+ "updated_at": "2026-07-19T13:02:48+00:00",
12
  "root": {
13
  "slug": "index",
14
  "title": "Reproduction: SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks?",
 
70
  }
71
  ]
72
  },
73
+ "agent_view_tokens": 9923,
74
+ "revision": "1784466168039888022"
75
  }
pages/deep-verification/page.md CHANGED
@@ -21,3 +21,20 @@ We went deeper on three things that couldn't be verified from the public dataset
21
  - **All overlapping n-grams are generic boilerplate** (e.g., 'users should be able to', 'steps to reproduce', 'there is no way to')
22
 
23
  **Verdict: Strong evidence for contamination resistance.** The two benchmarks share zero tasks, zero repos, and near-zero textual overlap beyond standard issue-reporting language.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
21
  - **All overlapping n-grams are generic boilerplate** (e.g., 'users should be able to', 'steps to reproduce', 'there is no way to')
22
 
23
  **Verdict: Strong evidence for contamination resistance.** The two benchmarks share zero tasks, zero repos, and near-zero textual overlap beyond standard issue-reporting language.
24
+
25
+
26
+ ---
27
+ <!-- trackio-cell
28
+ {"type": "markdown", "id": "cell_88d4f77d10ad", "created_at": "2026-07-19T13:02:44+00:00", "title": "Eval Repo Evidence"}
29
+ -->
30
+ ### 2. Eval Repo Evidence (indirect count verification)
31
+
32
+ **Method:** Analyzed the official eval repo ([scaleapi/SWE-bench_Pro-os](https://github.com/scaleapi/SWE-bench_Pro-os), 480 stars, 93 forks) via GitHub API for indirect evidence of the full 1,865/41 count.
33
+
34
+ **Evidence found:**
35
+ - **run_scripts directory: 1,000+ entries** (GitHub API paginated at 1,000; this is more than the 731 public instances, confirming the full dataset is larger)
36
+ - **instance_dockerfile directory: 731 entries** (exactly matches the public dataset)
37
+ - **Eval script references ** (not publicly available)
38
+ - **Separate leaderboards:** public ([scale.com/leaderboard/swe_bench_pro_public](https://scale.com/leaderboard/swe_bench_pro_public)) and commercial ([labs.scale.com/leaderboard/swe_bench_pro_private](https://labs.scale.com/leaderboard/swe_bench_pro_private))
39
+
40
+ **Conclusion:** The eval repo infrastructure contains run scripts for 1,000+ instances (exceeding the 731 public set), confirming the full 1,865-instance dataset exists server-side. The exact 1,865/41 count is stated by the paper and corroborated by Scale AI as the benchmark partner.