The tests reported passing even though there was an attribute error, i.e. the tests failed.

I spent a few hours on the source of the traceback and think I understand the problem and can fix it. Since I can't check in any of my alpha 4 bugs until I can run the functional tests, I think we should promote the traceback problem to alpha 4 so I can fix it.

I'm happy to postpone the CATS bug until after Alpha 4, but otherwise I think it should have a pretty high priority.

John

Heikki Toivonen wrote:
John Anderson wrote:
  
I'm currently not able to successfully run the functional tests on
Windows with no added changes, even though they seem to be passing on
the tinderbox. See the failure below
    

Does the test framework actually report that tests failed for you?
Because when I run them I see this traceback but the tests report
success. This is bug https://bugzilla.osafoundation.org/show_bug.cgi?id=6782

This probably started happening soon after my checkin to make perf and
sharing tests use the same code. I saw that error a day or two before I
checked in, but when I updated my tree before checkin to run tests it
was gone. Then a while after the checkin I updated my tree and started
seeing it again.

The bug above is about the bug in CATS for not noticing this. Of course,
we also have the bug about why the traceback itself is happening. I've
been looking, but haven't got a clue so far. Any ideas?

  

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to