-
School 0.4.2 Stable
released this
2026-11-13 22:55:12 +00:00 | 0 commits to main since this releaseSchool 0.4.2: the finish check sees where the work really landed
Two ways a goal run could look finished while the file that counts was broken or gone, both found in benchmark runs
of the local Flash Next model.A test that passed somewhere else no longer settles the real file
A model copied the file it was fixing into a scratch folder, fixed the copy, ran the tests there until they passed,
and stopped. The finish check accepted it, because a run had passed after the last change. The real file was left at
7 of 14 hidden checks; the scratch copy would have scored 11.- A passing run now settles only the code of the folder it ran in.
- A file changed outside that folder stays owed, but only when that folder holds its own copy of it, so the usual
cd tests && pyteststill settles the code above it. - The model is told in the same step which file is still owed and why.
A file the chat wrote and a command deleted is owed again
To replace a whole file, models sometimes delete it with a shell command and write it again. One run was cut off in
between and ended with the file gone and its own tests green: 0 of 14. Deleting a file this chat wrote now puts it
back on the list of what is owed, so the run cannot finish until it exists again. The pattern appeared in 40 of 386
benchmark runs; in live runs the note fired twice, both times correctly, and the model restored the file next step.For contributors
scripts/fast-tests.shruns the four test suites in parallel (41 s down to 15 s);--allruns every crate that
builds on the machine, 1,490 tests in about 100 s.Downloads