mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-05-08 03:01:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

test(kanban): backdate task_runs.started_at alongside tasks.started_at

Browse source 
After #19473 landed (enforce_max_runtime reads from task_runs.started_at
rather than tasks.started_at), a regression test added earlier still
only backdated the tasks column. Backdate both so the test is robust
regardless of which column the enforcer reads from.
This commit is contained in:
Teknium 2026-05-05 15:16:32 -07:00
parent b28ab4fc3f
commit 8a1a42d098
1 changed files with 12 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
tests/hermes_cli/test_kanban_core_functionality.py
View file

@ -3237,10 +3237,21 @@ def test_enforce_max_runtime_increments_consecutive_failures(kanban_home, monkey
)
kb.claim_task(conn, tid)
kb._set_worker_pid(conn, tid, os.getpid())
# Since PR #19473 (salvaged) changed enforce_max_runtime to read
# from task_runs.started_at (per-attempt) rather than
# tasks.started_at (lifetime), we need to backdate BOTH to
# guarantee the timeout fires regardless of which column the
# query pulls from.
with kb.write_txn(conn):
long_ago = int(time.time()) - 30
conn.execute(
"UPDATE tasks SET started_at = ? WHERE id = ?",
(int(time.time()) - 30, tid),
(long_ago, tid),
)
conn.execute(
"UPDATE task_runs SET started_at = ? "
"WHERE id = (SELECT current_run_id FROM tasks WHERE id = ?)",
(long_ago, tid),
)
before = kb.get_task(conn, tid)
assert before.consecutive_failures == 0