-
Notifications
You must be signed in to change notification settings - Fork 87
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
Debug ChainDB QSM failure where only the SUT iterator is exhausted #3999
Comments
The sequence of commands in the failing example looks like this.
The value of the security parameter is 2 (TODO: check this). The diagram depicts the presumed state of the system just after step 11. Note that:
graph LR
G-->B1(B1)
G-->B2
B2-->B3(B3)
B3-->B4(B4)
B2-->B8
B8-->B6
B6-->B9(B9)
B9-->B10(B10)
classDef streamed fill:red,stroke:red, stroke-width:3px
class B2 streamed
classDef invalid fill:gray
class B1 invalid
classDef to_stream stroke:red, stroke-width:3px
class B3 to_stream
class B4 to_stream
|
This is a simpler example that fails in the same way: graph LR
G-->B1
B1-->B2(B2)
B2-->B3(B3)
B1-->B4
B4-->B5
B5-->B6(B6)
B6-->B7(B7)
classDef to_stream stroke:red, stroke-width:3px
class B1 to_stream
class B2 to_stream
class B3 to_stream
Strangely enough, the SUT iterator is not exhausted in the following example. Here the observable behaviour of the model and the SUT is the same: graph LR
G-->B1
B1-->B2(B2)
B2-->B3(B3)
B1-->B4
B4-->B5(B5)
B5-->B6(B6)
classDef to_stream stroke:red, stroke-width:3px
class B1 to_stream
class B2 to_stream
class B3 to_stream
|
That fails (after about 10seconds of test execution) with:
This Issue is to determine the cause of the failure (I suggest checking for related comments/TODOs in the test code) and fix it.
The text was updated successfully, but these errors were encountered: