-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix configuration generation #126
Conversation
@ChristianKaltenecker Do you have an idea what is wrong with the solver here? |
For some reason, this caused other configs to appear multiple times during enumeration.
This caused 2 issues: - either first config was skipped or getCurrentConfig would always point to the next configuration - getAllValidConfigurations or getNumberValidConfigurations produce incorrect results if called after any call to getNextConfiguration() The last point is an issue with the Solver API and this is a quick-fix for the Z3Solver implementation that returns an error in that case.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## vara-dev #126 +/- ##
============================================
- Coverage 89.67% 89.63% -0.05%
============================================
Files 73 73
Lines 6991 6982 -9
============================================
- Hits 6269 6258 -11
- Misses 722 724 +2 ☔ View full report in Codecov by Sentry. |
This implementation is quite hacky and requires a redesign of the Solver API to be fixed properly.
This issue is more complicated than assumed. The current state of this PR should be considered a quick-fix. Do not merge until it is properly resolved. |
That means that model enumeration is no longer part of the solver interface, but should be done using the ConfigurationFactory and ConfigurationIterator.
This is now ready for review. |
Unittest for https://github.com/se-sic/VaRA/issues/1043