Skip to content

fix(worker): one-shot run exits 0 after a successful pass#248

Open
marktech0813 wants to merge 1 commit into
mini-router:mainfrom
marktech0813:fix/168-oneshot-exit-0
Open

fix(worker): one-shot run exits 0 after a successful pass#248
marktech0813 wants to merge 1 commit into
mini-router:mainfrom
marktech0813:fix/168-oneshot-exit-0

Conversation

@marktech0813

Copy link
Copy Markdown

Summary

One-shot eval_backend.worker passed `process_once`'s did-work signal (`1` when a job ran) straight to `SystemExit`, so successful evaluations exited as failures.

Call `process_once` then `SystemExit(0)`; genuine failures still raise.

Closes #168

Test plan

  • Unit test: one-shot path exits 0 when `process_once` returns 1

Made with Cursor

process_once returns a did-work signal for --loop sleep, not an exit
status. Passing it to SystemExit made successful jobs look like failures.

Closes mini-router#168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

worker: one-shot (non --loop) run exits 1 on success, so supervisors see every processed job as a failure

1 participant