You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take a known good Essence model, run Conjure to solve it.
Run Conjure on it again, this time with the -qi flag, which (per a separate bug report) trips Conjure's bug message mid-compile.
Attempt to run Conjure "normally" again on the model.
This returns the output:
Using cached models.
No solutions found.
Multiple eprime models found in the output directory, not copying solutions.
In actuality, there are no Essence' files in conjure-output at this stage.
More generally, this occurs whenever a bug prevents Conjure from completing compilation to Essence' between "good" runs. For example, I have also demonstrated this behaviour by taking a file with a line in it that causes Conjure to crash (specifically my toMSet example from a separate bug report) and commenting/uncommenting the bad line between runs.
The behaviour is also the same if you just delete the .eprime file, so I assume this is just a way for #495 to manifest from Conjure deleting the file but not replacing it.
The text was updated successfully, but these errors were encountered:
Probably the simplest way to recreate this issue:
-qi
flag, which (per a separate bug report) trips Conjure's bug message mid-compile.This returns the output:
In actuality, there are no Essence' files in
conjure-output
at this stage.More generally, this occurs whenever a bug prevents Conjure from completing compilation to Essence' between "good" runs. For example, I have also demonstrated this behaviour by taking a file with a line in it that causes Conjure to crash (specifically my toMSet example from a separate bug report) and commenting/uncommenting the bad line between runs.
The behaviour is also the same if you just delete the
.eprime
file, so I assume this is just a way for #495 to manifest from Conjure deleting the file but not replacing it.The text was updated successfully, but these errors were encountered: