Skip to content
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

Failed Minizinc unit tests #40

Open
MaxOstrowski opened this issue Oct 3, 2021 · 1 comment
Open

Failed Minizinc unit tests #40

MaxOstrowski opened this issue Oct 3, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@MaxOstrowski
Copy link
Member

Minizinc unit tests of the same hash fail to unknown cause.

@MaxOstrowski MaxOstrowski added the bug Something isn't working label Oct 3, 2021
@MaxOstrowski MaxOstrowski self-assigned this Oct 3, 2021
@MaxOstrowski
Copy link
Member Author

MaxOstrowski commented Oct 4, 2021

This is due to output bevaviour.
For some tests the expected output is:

x = 10;
----------

but we output

x = 10;
----------
%%%mzn-stat: models=1
%%%mzn-stat: time=0.038
==========

The last line states that the search was complete. For clasp, a search for 1 model only is complete, for minizinc, it is not. Currently I would need to parse the input (time costly) to check for optimization statements to make a correct decision for the output. Maybe using the python interface of clingcon can help determine the actual output status...

Edit: Models : 1+ the + could be used to determine search is not yet complete. Unfortunately, the asserting tests are all trivial for preprocessing s.t. clasp already can determine that there exists only exactly one model.

Fazit: I do not know how to fix this, the output format of minizinc is hard to produce given the output of such a "clever" system such as clasp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant