search

jariba / europa-pso

Automatically exported from code.google.com/p/europa-pso
1 stars 0 forks source link

Exception thrown depends on order of NDDL lines #113

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Unzip the attached example (a minor variant of hello world NDDL).
2. Run 'make clean; make'
3. You should see the following exception:

Solvers/base/FlawManager.cc:506: Error: 
m_db->getConstraintEngine()->constraintConsistent() is false
        Must be propagated and consistent.
PSEngine failed:Must be propagated and consistent.

Now, if you take these three lines of NDDL:

int x;
float y = 0.5;
eq(x, y);

and move them up two lines (ie right after the 'close();') then when you run, 
you don't get the exception although the solver seems to be flailing (as it 
just keeps running).

Original issue reported on code.google.com by tristanb...@gmail.com on 5 Mar 2011 at 1:36

GoogleCodeExporter commented 8 years ago

Original comment by javier.barreiro@gmail.com on 17 Aug 2011 at 7:53

GoogleCodeExporter commented 8 years ago 
this may be related to issue 112?

Original comment by javier.barreiro@gmail.com on 17 Aug 2011 at 7:56

GoogleCodeExporter commented 8 years ago

Original comment by tristanb...@gmail.com on 31 Aug 2011 at 6:21

GoogleCodeExporter commented 8 years ago

Original comment by javier.barreiro@gmail.com on 30 May 2012 at 5:26

GoogleCodeExporter commented 8 years ago 
Tristan, I know it's been... *ahem* three and a quarter years or so, but do you 
have a case around that replicates this?  There wasn't anything attached to the 
original ticket.

Original comment by miata...@gmail.com on 15 Aug 2014 at 6:34

GoogleCodeExporter commented 8 years ago 
I obviously had a case that I intended to attach but didn't do so.  Now I'm 
unable to find it anywhere, or even to guess as to what it might have looked 
like.  Given that, and the fact that this is the same exception as ticket 112, 
which has been addressed, I suggest closing this ticket (Invalid?  WontFix?) 

My apologies.

Original comment by tristanb...@gmail.com on 20 Aug 2014 at 5:43

GoogleCodeExporter commented 8 years ago 
No worries.  We're the ones who failed to address it in a timely fashion =-).  
I'm going to close this as NoRepro until we see something like it again.

Original comment by miata...@gmail.com on 22 Sep 2014 at 5:00