Billard e9b3b8e820 fix(cron): treat empty agent response as error in last_status (fixes #8585) ... When a cron job's agent run completes but produces an empty final_response (e.g. API 404 from invalid model name), the scheduler now marks last_status as "error" instead of "ok", so the failure is visible in job listings. Previously, any run that didn't raise an exception was marked "ok" regardless of whether the agent actually produced output.		2026-04-16 06:49:57 -07:00
..
__init__.py	test: add unit tests for 8 modules (batch 2)	2026-02-26 13:54:20 +03:00
test_codex_execution_paths.py	refactor(tests): re-architect tests + fix CI failures (#5946)	2026-04-07 17:19:07 -07:00
test_cron_inactivity_timeout.py	fix(cron): replace wall-clock timeout with inactivity-based timeout (#5440)	2026-04-05 23:49:42 -07:00
test_cron_script.py	fix(cron): harden scheduler against path traversal and env leaks	2026-04-06 12:42:16 -07:00
test_file_permissions.py	refactor(tests): re-architect tests + fix CI failures (#5946)	2026-04-07 17:19:07 -07:00
test_jobs.py	feat(cron): track delivery failures in job status (#6042)	2026-04-07 22:49:01 -07:00
test_scheduler.py	fix(cron): treat empty agent response as error in last_status (fixes #8585)	2026-04-16 06:49:57 -07:00