run_phase processes 5 items, each inside its own raise and drop of an objection. Item 2 fails validation. Its error-handling path works on its own; the trouble is how it combines with the rest of the loop body.
Right nowThe test never gets past item 2.
Fix the code so all 5 items are processed, the bad one included, without the simulation dying.
One working answer: brokenbench's own fix for this exercise. Try a few runs first.
What changes, against the code you started with:
docker run --pull always --rm -p 127.0.0.1:8787:8787 ghcr.io/adibis/brokenbench-runnerLooking for a runner on this computer…
The first start downloads about 250 MB; after that it starts in seconds and only downloads again when there's an update. Your code goes to the runner on your computer, not to chipdv.io.