test lib in MR
currently we does not test tests/lib
in MR only in the scheduled tests thats unfortunate for lib development.
i rememmber we did this because of the heavy test (and possible warnings) from rolling..
i suggest we should either rework the test directory structure (tests/slow
and tests/fast
) or something like this or alwys run all tests.