TemporalReasoningUTest failures
linas opened this issue · 2 comments
Nil,
TemporalReasoningUTest is failing after what should have been a trivial change to the AtomSpace. It passes on this commit: 78b7f37a7c18b244a9e55d91054ddc5857e6a2cb and it fails on the next one: 5848cde3ddc46279a26e413e846c8018880cebb0 The only difference between these two commits are that five new atom types were added. I can't imagine why adding some more Atom types causes TemporalReasoningUTest to fail.
More precisely, it hangs and spins -- it eats CPU time, but makes no forward progress. The last thing it prints is this:
[DEBUG] [URE] Selected and-BIT for fulfillment (fcs value):
[ac47efeeeec27302][4]
and then hangs.
I'm focusing on something else, will get back to that (and other pending issues) after a few days.
See also issue opencog/ure#120 -- Identical symptoms: minor change in the AtomSpace caused ForwardChainerUTest to fail. I was able to work around this by setting randGen().seed(3); in the unit test. Other seed values lead to failures.