You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected: a campaign.cancel_requested event with actor human, the in-flight job runs to completion, then campaign.ended with stop_reason: "cancelled".
Note that an immediate scancel isn't implemented yet (which is why the in-flight job still is allowed to complete).
Crash drill
Start a new campaign from a fresh branch.
While an experiment's job is RUNNING, find and kill the server:
pkill -9 -f 'bin/faberon$'
(really brute force it like this, don't just hit Ctrl-C in the pane where you started faberon)
In the pane that originally started faberon, you'll see a short message "Killed".
Then restart it:
cd~/git/autoresearch
faberon
Expected: the campaign resumes on its own. The running job is not resubmitted (submission is idempotent on the job name), the poll picks up where it left off, and the loop continues. Do it a second time right after a experiment.judged event to cover the between-experiments case.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Use the runbook for the current version instead.
To test the robustness of the v0.2 infrastructure, both for an unexpected crash, as well as for a human-intended cancel.
cf. #23 for all setup and how to start a campaign. Make sure to run 0.2.2:
Cancel drill
Start a new campaign from a fresh branch. Once its first job is running:
Expected: a
campaign.cancel_requestedevent with actorhuman, the in-flight job runs to completion, thencampaign.endedwithstop_reason: "cancelled".Note that an immediate
scancelisn't implemented yet (which is why the in-flight job still is allowed to complete).Crash drill
Start a new campaign from a fresh branch.
While an experiment's job is RUNNING, find and kill the server:
pkill -9 -f 'bin/faberon$'(really brute force it like this, don't just hit Ctrl-C in the pane where you started
faberon)In the pane that originally started
faberon, you'll see a short message "Killed".Then restart it:
Expected: the campaign resumes on its own. The running job is not resubmitted (submission is idempotent on the job name), the poll picks up where it left off, and the loop continues. Do it a second time right after a
experiment.judgedevent to cover the between-experiments case.All reactions