Skip to content

TemporalReasoningUTest failures #60

Description

@linas

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions