[1]: https://skiplabs.io
Very cool to see a team use Jepsen for super early pre-release testing of the system.
I wonder if you wish you had waited for the runtime to be a bit more stable, or you feel this was already well worth the effort, even with some of the identified failures being in "known incomplete" areas? (I could see either side of the argument - waiting longer might give you more valuable failures, but testing early gives you a chance to catch problems before they become baked into the foundation and become more difficult to fix...)
Another tool that feels like sci-fi to me any time I hear a mention of it, is Antithesis [1] - written by the people who built FoundationDB. Could be another interesting integration to investigate in the future to help bulletproof the language runtime?
I wonder how this will pan out... very interesting to see new approaches being explored.
That's... uh... a pretty bold description for a tool where you are in fact outsourcing the "imagination" part to the machine.
Thanks for sharing this, so cool to learn about it!
Deleted Comment
> New regulations for the elections of the doge introduced in 1268 remained in force until the end of the republic in 1797. Their intention was to minimize the influence of individual great families, and this was effected by a complex electoral machinery. Thirty members of the Great Council, chosen by lot, were reduced by lot to nine; the nine chose forty and the forty were reduced by lot to twelve, who chose twenty-five. The twenty-five were reduced by lot to nine, and the nine elected forty-five. These forty-five were once more reduced by lot to eleven, and the eleven finally chose the forty-one who elected the doge.[31] > --wikipedia
Or, with the subject matter being tech, most potential readers are fluent anyway?