TLC reports zero coverage for conjunct of the next-state action
See original GitHub issueTLC reports 0 coverage for the indicated conjunct of the next-state action below:
VARIABLE x
Spec == /\ x = 0
/\ [][/\ x' = (x+1)%5
/\ x' = (x+1)%5 \* <- 0 coverage
]_x
This is an oversimplification of a problem that occurred in a real spec. A slightly more complicated example indicates how it can arise in practice.
/\ A
/\ \/ /\ x' # x
/\ ...
\/ /\ x' = x \* <- 0 coverage
/\ ...
where
A == \/ /\ ...
/\ x' = ...
/\ ...
\/ /\ ...
/\ x' = x
/\ ...
Related, TLC reports zero coverage for the (automatically) generated vars = <<x,y,z>>
definition of PlusCal unless vars
appears as part of an UNCHANGED statement (see issue #152).
Issue Analytics
- State:
- Created 6 years ago
- Comments:24 (24 by maintainers)
Top Results From Across the Web
tlaplus/MP.java at master - GitHub
Any kind of String used as a message reported to the user should be replaced with ... b.append("TLC could not determine if the...
Read more >Specifying Systems - Leslie Lamport
The next-state action is satis ed by a Send(d) step, for some d in Data, or ... The TLC model checker, described in...
Read more >Specifying Systems - Software Engineering Documentation
The next-state action is satisfied by a Send(d) step, for some d in Data, or ... The TLC model checker, described in Chapter...
Read more >procedures manual - for joint committees
Certain staff support and other services are available at no charge to the ... complete the TLC Receiving Report included with the supply...
Read more >Codecov, Github actions and Angular 11 "No coverage report ...
This is because default generated coverage report is not supported by codecov. Simple solution is just adding lcov reporter to your config.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please add a JUnit test with a spec that shows the problem. The test class should be derived from https://github.com/tlaplus/tlaplus/blob/master/tlatools/test/tlc2/tool/liveness/ModelCheckerTestCase.java (don’t mind liveness in the package name)
Obsolete due to f11c4ad92b0cdb5c3b1d918055c17bf64c8b0a93