The judge rewrites the motion probe instead of running it #416
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens. run 181's judge wrote its own
getAnimations()freeze;clock.stepappears only in the brief.Fix. name the motion probe at the animation criterion itself, with its one-line call, and put the probes block before "How to end".
Done when. a judge transcript calls the pasted probe.
From run 181, the verifying run after #407; the log is
docs/design/measurements/work/run-180/findings.md.Shipped in PR #421 (
ff9381d8), changebriefs-after-run-181. The judge's rules gained "For motion shorter than a turn, run the motion probe below, then take the screenshot: never write a freeze of your own", and the probes block moved up to follow the rules, before "Write the report as you go" (it had sat after it, before "How to end").tests/engine/test_see_motion.pybuilds the whole judge brief and holds the order. Done when a judge transcript calls the pasted probe: the next Scratch run.