-
Notifications
You must be signed in to change notification settings - Fork 21
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
False positive result on Sat4j 2018/10/25 experiment #84
Comments
I ran Descartes after the last commit on Sat4j: https://gitlab.ow2.org/sat4j/sat4j/commit/309b935d53606fcba2f4e009da82590c993a857d This commit was aiming to cover the createClause() method in https://github.com/STAMP-project/descartes-usecases-output/tree/master/OW2/Sat4j/201810251534/issues/org.sat4j.minisat.constraints.MixedDataStructureDanielWLConciseBinary The new results are : https://github.com/STAMP-project/descartes-usecases-output/tree/master/OW2/Sat4j/201811081117 Results show that not only the targeted method is resolved, but also this one ( run() ) is no more in the report. But now, we have the onFinishWithAnswer() in the output (which was not detected previously) |
The infinite loop also occurs when removing the body of |
Could you check that the test cases that detect the methods in the original test suite are also executed when running Descartes? |
@assadOW2 any news on this? Did you try the previous solution? |
Hi @oscarlvp ! |
Characteristics
Description
This refers to this output: https://github.com/STAMP-project/descartes-usecases-output/tree/master/OW2/Sat4j/201810251534/issues/org.sat4j.tools.RunnableSolver
When manually commenting all the run() method, original test suite detects a time out, resulting in a failure. This is due to the fact that without onFinishWithAnswer() running, there is an infinite loop.
The method should not appear in Descartes output since this is not a real survivor.
Steps to reproduce
Other files and URLs
Relationships
Help on issue template
Preview to follow the link or open file .github/ISSUE_DOC.md
The text was updated successfully, but these errors were encountered: