-
Notifications
You must be signed in to change notification settings - Fork 31
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
java.lang.AssertionError: Assert failed: i #8
Comments
Additional info: almost exclusively there seems to be a runtime error in the client's setup method when this assertion fails, but I'll validate further. |
On 01/05/2016 11:30 AM, Balint Pato wrote:
Looks like you had an initial value that was nil, but specified in the model the --Kyle |
Thanks, Kyle, it was a problem with the initial value, and that's why it's just happening sometime (when the first operation in the history is a read), however, the problem was a casting issue:
This assertion error always going to come up for invalid analyses failing on the very first operation as in the final-path "All paths start with the previous completion operation" which is nil in this case. |
Ohhhh hang on, haha, there's another closely related error in knossos.model.memo where precomputed states don't cover reachable states, but that's not the error you hit. Yeah, I agree, we should, um, do something sensible here. |
Hi, Kyle, do you have any efforts on this problem? I have encountered |
@gaodq There are a lot of assertions in Knossos, and without the actual error message and trace it's hard for me to say. I've made some improvements to error handling in the latest knossos release, which went out yesterday, but I can't tell you whether that will cover your problem or not. |
Hi,
Every now and then, the execution of knossos after jepsen tests throws the exception below. I copied the history as well. Am I doing something stupid?
Thanks,
Balint
I'm using in the jepsen test the simple cas model:
The exception:
history of operations is the following (simple mix of read and write ops):
The text was updated successfully, but these errors were encountered: