unit tests should really cover only one given functionality. although first i've liked this idea of covering everything at once, but actually it'd be better to split each of these into a separate unit test, so something like:
 * ```TEST(LibLinearTest, train_L2R_LR)```
 * ```TEST(LibLinearTest, train_L2R_L2LOSS_SVC_DUAL)```
 * ```TEST(LibLinearTest, train_L2R_L2LOSS_SVC)```
... and so on.

because this way we can right away identify which method failed.
You can do this actually by writing a generated unit test. see for example ```tests/unit/base/clone_unittest.cc.jinja2``` and the corresponding ```tests/unit/base/clone_unittest.cc.py``` and the ```tests/unit/CMakeLists.txt```