-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
State machine #29
State machine #29
Conversation
I fixed the dot graph visualization so that properly labels state transitions now.
@sdandam I'd suggest pulling this branch down to your local machine and running the tests to get a feel for what this is doing. It also might be helpful to take the digraph and print it as a svg and check what transitions are happening. I don't think this is perfect yet but it's working decently well at this point that I want to start the review process. |
resolves #13
3e7ac97
to
3f46318
Compare
Well this is a bummer. I ran into a cargo bug: rust-lang/cargo#4866 and it'll require us staying on nightly until it gets resolved. Not sure what else we can do it about it. I tried various things and nothing helps with getting this to compile on stable. |
Since the tests run in parallel by default I had to introduce a bunch of random variables and a mutex to make sure the tests weren't all writing to the same loopback backing file or grabbing the same loopback device from the system.
Awesome to see this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't run the tests yet, but have read through it. Looks good to me.
No problem. We've got a lot more testing to do before this makes it into production |
This drastically changes how test_disk functions and changes it over to using a state machine. The code will print out a digraph when tests are run so that the logic tree can be visualized.