Neither am I.

There might be one explanation... The test suite changes the default JVM time zone multiple times during its execution, to simulate different real-world scenarios. However, the MySQL JDBC driver caches the JVM time zone in a static variable, which might introduce side-effects between tests.

Peter Mackay Could you please try setting the cacheDefaultTimezone JDBC driver property to false, to rule out the problem mentioned above?

The setting is provided through the JDBC URL. For example, instead of this:

jdbc:mysql://127.0.0.1/hibernate_orm_test?useSSL=false

Use this:

jdbc:mysql://127.0.0.1/hibernate_orm_test?useSSL=false&cacheDefaultTimezone=false