Re: Trellis: undetected circularity via optional rules

Grant Baillie <grant-6zGkXsw2EZWGJGYlWa3Ukdi2O/[email protected]> Thu, 16 Apr 2009 08:29:20 -0700
Newsgroups gmane.comp.python.peak
Message-ID <[email protected]>
On 15 Apr, 2009, at 11:31, Sergey Schetinin wrote:

> Now I wonder if this will break any trellis properties, like circular
> maintain rules that don't set conflicting values (the rules might
> initialize each other even if they are not optional, when the
> component is being initialized). The tests fail, but they always hang
> up for me anyway, so I can't really use that as a reference.
>
>
> So I have a question: for how many people in this list trellis tests
> do run successfully?

They hang for me, too (on Mac OS X 10.5). After I disable the tests

test_trellis.TestReactorEventLoop.testSequentialCalls
test_trellis.TestTasks.testNoTodoRollbackIntoTask

I still get a bunch of failures in test_sets.TestUpdateOps (although  
these seem to pass when run by themselves).

--Grant