-
Notifications
You must be signed in to change notification settings - Fork 37
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
Causal replay #156
Causal replay #156
Conversation
118759d
to
f6ba23b
Compare
f6ba23b
to
a63bbdf
Compare
}) | ||
.expect_err("test should panic"); | ||
let output = result.downcast::<&str>().unwrap(); | ||
assert_eq!(*output, "expected panic"); |
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.
Could you also add an assert about steps_skipped
to test that functionality too?
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'm not sure how to do this (easily): Runner::new
takes the scheduler we construct, so there is no access to it afterwards.
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.
Okay for now. Maybe we can find a way to get additional metrics through the metrics scheduler
}) | ||
.expect_err("test should panic"); | ||
let output = result.downcast::<&str>().unwrap(); | ||
assert_eq!(*output, "expected panic"); |
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.
Similar comments here: add assertions for me()
and steps_skipped
a63bbdf
to
83cdcef
Compare
Head branch was pushed to by a user without write access
83cdcef
to
188de43
Compare
An attempt to add causal dependency to the replay scheduler. To use this,
set_target_clock
should be invoked on aReplayScheduler
instance with the clock of the failure event (provided as a slice of integers). Some things to resolve still:Task
s rather than justTaskId
s. I think we discussed that schedulers should generally have access to more information about tasks, so if this is the approach we take, theTask
interface might deserve some more cleanup. Even more so if schedulers are eventually intended to be defined in a separate crate.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.