H2 tests actually run quite a long time. We may have to split tests into multiple parts to avoid these timeouts.
I think it is a good idea to split the tests into matrix [1] by settings: - in-memory + embedded - in-memory + networked - on-disk + embedbed - on-disk + networked This way we will have a clearer picture of what exactly behaves badly. [1] https://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix Sergi 2016-09-01 11:56 GMT+03:00 Noel Grandin <[email protected]>: > Note that there are a couple of OOM tests, so you need to make sure that > the Java for the tests runs with limited heap, i.e. with the -Xmx parameter. > > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
