No.. one issue is that app1.FormTests.datefield_select_newmonth_samedate() is perhaps a bit unreliable with waits not always succeeding. The current problem though is that the build on Travis is not cleaning the classpath caches. There are some remnants of the previous version Hibernate on the classpath that throws it off. I got the same problem until I did clean, otherwise I claim there's nothing wrong. I don't have permissions to modify the Travis build, was that Jochen who set it up?
Kalle On Sat, Jul 9, 2016 at 9:27 AM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > Hmm it's the :tapestry-core:testWithPrototype that's failing... looking. > > Kalle > > On Fri, Jul 8, 2016 at 4:03 PM, Travis CI <bui...@travis-ci.org> wrote: > >> Build Update for apache/tapestry-5 >> ------------------------------------- >> >> Build: #125 >> Status: Still Failing >> >> Duration: 14 minutes and 51 seconds >> Commit: 9ae5c2b (master) >> Author: kaosko >> Message: TAP5-2556: Upgrade Hibernate to 5.2 for T5.5 >> >> - update to 5.2.1.Final >> - fix compilation errors, test suite ok >> >> View the changeset: >> https://github.com/apache/tapestry-5/compare/d8120525e858...9ae5c2bb9c9f >> >> View the full build log and details: >> https://travis-ci.org/apache/tapestry-5/builds/143460786 >> >> -- >> >> You can configure recipients for build notifications in your .travis.yml >> file. See https://docs.travis-ci.com/user/notifications >> >> >
