AI & ML
DARE: Difficulty Analysis for Repair Enhancement
arXiv cs.SE0 views
arXiv:2611.05797v1 Announce Type: new Abstract: LLM-based coding agents are primarily evaluated by their solve rates. However, this metric does not reveal how difficult the solved tasks are or account for differences intask difficulty across benchmarks. Determining the difficulty of individual tasks by repeatedly running multiple agents is costly, while a predicted difficulty score alone provides limited guidance on what support an agent needs. To address these challenges, we propose DARE (Difficulty Analysis for Repair Enhancement), which integrates repair-task difficulty measurement, prediction, feature-group contribution analysis, and task-specific repair support. We define continuous task difficulty as the observed failure rate across multiple coding agents. The DARE difficulty model predicts this difficulty using 151 static features extracted from benchmark artifacts. The framework also analyzes the contributions of seven Repair-Task Feature Groups to identify the characteristics most salient to each task and uses this information to select task-specific agent support. We evaluate DARE on four benchmark partitions comprising 2,594 tasks. The difficulty model's aligned predictions achieve Spearman's $\rho$ = .476-.621 on held-out partitions, and the most salient Feature Groups vary across tasks and benchmarks. Furthermore, coding-agent experiments show improved repair success when support is matched to each task's salient Feature Group. These findings demonstrate that difficulty prediction and interpretation can lead to practical improvements in automated program repair (APR), while also providing a basis for difficulty-stratified agent evaluation, cross-benchmark comparisons, and identifying areas of repair capability that warrant further improvement.
Source:https://arxiv.org/abs/2611.05797PreviousHow Much Do Modern Embeddings Reveal? Inversion Attacks on Commercial Embedding ModelsNextCan LLM Agents Learn to Test? Maintaining Scoped Experience as Testing Evidence for Mobile GUI Testing
Related posts
TTHE: Test-Time Harness Evolution
0arXiv cs.SE
How the Misuse of a Dataset Harmed Semantic Clone Detection
0arXiv cs.SE
Reasoning-Trace Overflow in Code Generation: An Empirical Study of Explicit Reasoning Models
0arXiv cs.SE
RIDGE: State-Conditioned Reward Blending for Behavioral Coverage in Deep RL Game Agents
0arXiv cs.SE
MCP-Eco: A Linked Dataset of MCP Servers, Consumers, and Development Activity
0arXiv cs.SE
FedCSGA: Evolutionary Client Selection with Joint Statistical and System Heterogeneity in Federated Learning
0arXiv cs.DC