News for hackers. Stuff that matters.

A comment on Writing an OS in Rust: Async/Await. Parent comment

Re:Writing an OS in Rust: Async/Await by ccktlmazeltov on Monday March 30, 2020 @03:38PM (#22731482)
This is a huge issue when trying to fuzz async code also.
[ Parent | on HN ]
Re:Writing an OS in Rust: Async/Await by staticassertion on Monday March 30, 2020 @06:44PM (#22732960)
Dropbox does, essentially, fuzzing of Rust async code and it is determistic.

I couldn't find a post about it, sadly, but I know the information is out there somewhere.

[ Parent | on HN ]
Re:Writing an OS in Rust: Async/Await by ccktlmazeltov on Monday March 30, 2020 @10:00PM (#22734272)
source? Can't find anything on that either
[ Parent | on HN ]
Re:Writing an OS in Rust: Async/Await by staticassertion on Monday March 30, 2020 @10:48PM (#22734511)
https://dropbox.tech/infrastructure/rewriting-the-heart-of-o...

> The Control thread is designed to be entirely deterministic when its inputs and scheduling decisions are fixed. We use this property to fuzz it with pseudorandom simulation testing. With a seed for our random number generator, we can generate random initial filesystem state, schedules, and system perturbations and let the engine run to completion. Then, if we fail any of our sync correctness checks, we can always reproduce the bug from the original seed. We run millions of scenarios every day in our testing infrastructure.

[ Parent | on HN ]