Yashp2003 commited on
Commit
af8ad05
·
verified ·
1 Parent(s): 91c33b6

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 +25 -0
logbook.json CHANGED
@@ -8,7 +8,7 @@
8
  "icml2026-repro",
9
  "paper-uEVTdoAbnK"
10
  ],
11
- "updated_at": "2026-07-19T13:03:02+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": 10224,
74
- "revision": "1784466182026829323"
75
  }
 
8
  "icml2026-repro",
9
  "paper-uEVTdoAbnK"
10
  ],
11
+ "updated_at": "2026-07-19T13:03:16+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": 10499,
74
+ "revision": "1784466196114895058"
75
  }
pages/deep-verification/page.md CHANGED
@@ -55,3 +55,28 @@ We went deeper on three things that couldn't be verified from the public dataset
55
  **HF Job:** [Yashp2003/6a5cc999bee6ee1cf4ed1174](https://huggingface.co/jobs/Yashp2003/6a5cc999bee6ee1cf4ed1174)
56
 
57
  **Note:** Agent solve rate is outside the scope of this dataset audit. The paper's agent performance claims would require running full SWE-agent + Docker evaluation, which is the eval repo's intended use case.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
55
  **HF Job:** [Yashp2003/6a5cc999bee6ee1cf4ed1174](https://huggingface.co/jobs/Yashp2003/6a5cc999bee6ee1cf4ed1174)
56
 
57
  **Note:** Agent solve rate is outside the scope of this dataset audit. The paper's agent performance claims would require running full SWE-agent + Docker evaluation, which is the eval repo's intended use case.
58
+
59
+
60
+ ---
61
+ <!-- trackio-cell
62
+ {"type": "markdown", "id": "cell_6509a3fa962d", "created_at": "2026-07-19T13:03:13+00:00", "title": "Contamination Analysis Details"}
63
+ -->
64
+ ### Contamination Analysis Details
65
+
66
+ | Metric | Value | Interpretation |
67
+ |---|---|---|
68
+ | Instance ID overlap | 0 | Zero shared tasks |
69
+ | 5-gram overlap | 146 / 125,772 (0.12%) | Near-zero textual overlap |
70
+ | Repository overlap | 0 repos | Completely different codebases |
71
+ | Avg max similarity | 0.1094 | Very low (10.9%) |
72
+ | Max similarity | 0.1953 | No task above 20% similarity |
73
+ | Tasks > 50% similar | 0 / 30 | No semantic duplicates |
74
+
75
+ **Top overlapping 5-grams** (all generic issue-report boilerplate):
76
+ 1. 'users should be able to' (13x in Pro)
77
+ 2. 'what did you expect to' (11x)
78
+ 3. 'steps to reproduce 1. run' (9x)
79
+ 4. 'there is no way to' (8x)
80
+ 5. 'did you expect to happen?' (6x)
81
+
82
+ None of these contain domain-specific or task-specific content -- they are standard GitHub issue template language shared across any two software bug-reporting datasets.