Thank you, Greg.
Due to lack of some shared libraries i decided to compile it once again, I
will then rerun tests and see if something changed. In case I succeed I can
share binaries as compiling RDkit on Raspberry takes some time (of course
you can cross compile it but this makes this process even harder for
inexperienced users like me).
Kind regards,
Michal Nowotka
On Tue, Jun 18, 2013 at 1:02 AM, Greg Landrum <greg.land...@gmail.com>wrote:
> Here is the failing test from that output (ctest does not make this as
> easy as it could be):
>
> 76: FAIL: test_timeout (__main__.TestTimeout)
> 76: ----------------------------------------------------------------------
> 76: Traceback (most recent call last):
> 76: File "UnitTestMCS.py", line 263, in test_timeout
> 76: self.assertTrue(t2-t1 < 0.5, t2-t1)
> 76: AssertionError: 0.593647956848
> 76:
> 76: ----------------------------------------------------------------------
> 76: Ran 42 tests in 3.744s
> 76:
> 76: FAILED (failures=1)
>
> The error occurs due to a timeout in the mcs code; given that the
> raspberry pi is "somewhat" underpowered, this isn't that much of a
> surprise. I will try to figure out if it is possible to make that test more
> robust, but in the meantime I think your build is probably fine.
>
> -greg
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
