The user wants 2000 tasks, most of them ones Qwen cannot solve. New batch tasks are now measured on their branch first (3 Qwen trials each), and only HARD or MEDIUM tasks reach main; ROUTINE ones stay on the batch branches. A session cut by context_limit or output_limit counts as a failure for difficulty (user decision 2026-11-03); the trajectory stays incomplete. - Batch 26 (route D, real upstream fixes in embedded open-source projects): 7 HARD of 20 (coreJSON, littlefs, CANopen, coreMQTT, LwM2M, Zephyr ring, lwIP SNTP). Most failures are Qwen exhausting its context in the larger workspaces. - Batch 25 (HWE mutation repairs): 1 HARD and 1 MEDIUM of 56. - Batch 27 (spec-dense implementation tasks): 2 MEDIUM of the first 10. Each task comes from the exact commit Qwen measured, and its digest matches the measured one. Failure reasons are not yet reviewed, so difficulty is the automatic label. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
32 lines
685 B
JSON
32 lines
685 B
JSON
{
|
|
"id": "runtime-sensor-stop-mailbox",
|
|
"version": "1",
|
|
"family": "linux-userspace-abi",
|
|
"source": "hwe/syn-arm-002-mut-isr_block_injector-0",
|
|
"language": "C++17",
|
|
"template": "template",
|
|
"verifier": "verify.py",
|
|
"candidate_files": [
|
|
"include/sensor.hpp",
|
|
"src/codec.cpp",
|
|
"src/mailbox.cpp",
|
|
"src/session.cpp",
|
|
"src/catalogue.cpp"
|
|
],
|
|
"grader_files": [
|
|
"check.py"
|
|
],
|
|
"fixtures": {
|
|
"gold": "PASS",
|
|
"template": "FAIL",
|
|
"noop": "FAIL",
|
|
"cheat": "FAIL",
|
|
"cheat_read_grader": "FAIL",
|
|
"fix_callback": "FAIL",
|
|
"fix_eintr": "FAIL",
|
|
"mask_symptom": "FAIL",
|
|
"valid_staged": "PASS"
|
|
},
|
|
"timeout_seconds": 120
|
|
}
|