Ben, we need this decorator also for atom (it is something with BD which is probably nothing) - can you explain how to use it (or just send me to an example code)
Cheers
Barak

On Wed, Aug 15, 2012 at 11:16 AM, Ben Webb <ben@salilab.org> wrote:
On 8/15/12 11:02 AM, Barak Raveh wrote:
guys, let's try to get one day of TOTALLY clean tests :) can people in
charge of*cgal, isd and multifit *(Fast build only)** give a quick look

to see if they can quickly solve the test issues (the atom case is
known, and if other tests are solved, we'll handle that too). If there's
a complicated issue behind these failures, we can temporarily disable
those tests until the relevant person get to work on it.

That's exactly what I will do, now that I have the test infrastructure running properly again. The MultiFit failures are not simple ones, but I will fix them. The ISD tests have been broken since day one, but hopefully Yannick will get around to fixing them...

BTW, never disable tests by removing them or commenting out. There is an expected failure decorator you can use for such tests (or you can skip them if they only fail some of the time). Such tests get logged so we know we still have to fix them in future.

        Ben
--
ben@salilab.org                      http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
        - Sir Arthur Conan Doyle
_______________________________________________
IMP-dev mailing list
IMP-dev@salilab.org
https://salilab.org/mailman/listinfo/imp-dev



--
Barak