~bigbes/agents-dev · parade

main · last commit 13 days ago · 7g0stsfu

← Back to the parade

ah-2ef e2e suite rare timing flake (1 FAIL in ~5 runs observed 2026-07-18) Past Stand

status: closed P3 bug @Eugene Blikh
bd reopen ah-2ef
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-07-18T17:03:58Z
Started2026-07-18T17:28:20Z
Updated2026-07-18T18:15:54Z
Closed2026-07-18T18:15:54Z
Description
During wave-4 verification one 'go test -tags e2e ./e2e' run printed FAIL while 4 adjacent runs passed (12.6-13.3s). Failing subtest name was not captured (output was filtered). The suite has timing-sensitive subtests (500ms-deadline timeout path, stall watchdog). Next occurrence: rerun with -v, capture the failing subtest, then either widen its deadline margins or de-flake the poll. Not tied to wave-4 changes (harness timing predates them).

Depends on

No outgoing dependencies.

Depended on by

Nothing depends on this issue.

No comments.

Close reason

Merged (fix/runner, reworded from 5f70d17): Status() read events.jsonl before exit.json confirmed completion; a poll straddling a fast exit froze empty PiSessionID/CostUSD into the immutable run row. Both applyExit sites now re-parse the confirmed-complete stream. Reproduced under stress with instrumentation; 26/26 clean unstressed + 13 race runs clean; e2e x3 green at merge.
  • Eugene Blikh created the issue · 2026-07-18T20:03:57Z
  • Eugene Blikh claimed · 2026-07-18T20:28:20Z
  • Eugene Blikh closed the issue · 2026-07-18T21:15:53Z
    Merged (fix/runner, reworded from 5f70d17): Status() read events.jsonl before exit.json confirmed completion; a poll straddling a fast exit froze empty PiSessionID/CostUSD into the immutable run row. Both applyExit sites now re-parse the confirmed-complete stream. Reproduced under stress with instrumentation; 26/26 clean unstressed + 13 race runs clean; e2e x3 green at merge.
Stored rows — what this pane was built from, as read
issues 1 row
id ah-2ef
content_hash ff98b88593d96664a9626ff5ba7750acc64df6bde5526cca7d05a55ecc89e4aa
title e2e suite rare timing flake (1 FAIL in ~5 runs observed 2026-07-18)
description During wave-4 verification one 'go test -tags e2e ./e2e' run printed FAIL while 4 adjacent runs passed (12.6-13.3s). Failing subtest name was not captured (output was filtered). The suite has timing-sensitive subtests (500ms-deadline timeout path, stall watchdog). Next occurrence: rerun with -v, capture the failing subtest, then either widen its deadline margins or de-flake the poll. Not tied to wave-4 changes (harness timing predates them).
design
acceptance_criteria
notes
status closed
priority 3
issue_type bug
assignee Eugene Blikh
estimated_minutes NULL
created_at 2026-07-18T17:03:58Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-07-18T18:15:54Z
closed_at 2026-07-18T18:15:54Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason Merged (fix/runner, reworded from 5f70d17): Status() read events.jsonl before exit.json confirmed completion; a poll straddling a fast exit froze empty PiSessionID/CostUSD into the immutable run row. Both applyExit sites now re-parse the confirmed-complete stream. Reproduced under stress with instrumentation; 26/26 clean unstressed + 13 race runs clean; e2e x3 green at merge.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at 2026-07-18T17:28:20Z
is_blocked 0
events 3 rows
id 019f762f-4823-7217-b97b-b10938092085
issue_id ah-2ef
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-07-18T20:03:57Z
id 019f7645-98b2-7003-ac34-87a4576b493b
issue_id ah-2ef
event_type claimed
actor Eugene Blikh
old_value {"id":"ah-2ef","title":"e2e suite rare timing flake (1 FAIL in ~5 runs observed 2026-07-18)","description":"During wave-4 verification one 'go test -tags e2e ./e2e' run printed FAIL while 4 adjacent runs passed (12.6-13.3s). Failing subtest name was not captured (output was filtered). The suite has timing-sensitive subtests (500ms-deadline timeout path, stall watchdog). Next occurrence: rerun with -v, capture the failing subtest, then either widen its deadline margins or de-flake the poll. Not tied to wave-4 changes (harness timing predates them).","status":"open","priority":3,"issue_type":"bug","owner":"bigbes@gmail.com","created_at":"2026-07-18T17:03:58Z","created_by":"Eugene Blikh","updated_at":"2026-07-18T17:03:58Z"}
new_value {"assignee":"Eugene Blikh","status":"in_progress"}
comment NULL
created_at 2026-07-18T20:28:20Z
id 019f7671-2362-7a64-a939-4314ac5b06ed
issue_id ah-2ef
event_type closed
actor Eugene Blikh
old_value
new_value Merged (fix/runner, reworded from 5f70d17): Status() read events.jsonl before exit.json confirmed completion; a poll straddling a fast exit froze empty PiSessionID/CostUSD into the immutable run row. Both applyExit sites now re-parse the confirmed-complete stream. Reproduced under stress with instrumentation; 26/26 clean unstressed + 13 race runs clean; e2e x3 green at merge.
comment NULL
created_at 2026-07-18T21:15:53Z