The Sql ones look like they are testing DataSets which require the source files to be on the classpath. Sounds like the new setup isn't quite right but I haven't dived into into yet - perhaps the old build was also wrong in that regard.
On Mon, Dec 11, 2017 at 8:23 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: > BTW I have some tests failing with Indy: https://scans.gradle. > com/s/5hluytiiafifk/tests/failed > > At this point I'm not sure if it's a problem with the new setup, or that > it was uncaught before. > > 2017-12-11 11:10 GMT+01:00 Cédric Champeau <cedric.champ...@gmail.com>: > >> Thanks Daniel. >> >> Would you mind trying again? I have fixed the problem I think. >> >> Also we now have a `testWithIndy` task, so a single build is capable of >> testing both the normal and indy variants. >> >> 2017-12-11 10:22 GMT+01:00 Daniel.Sun <sun...@apache.org>: >> >>> >>> 1) apache-groovy-binary-3.0.0-SNAPSHOT.zip contains three >>> groovy-raw-3.0.0-SNAPSHOT.jar with same size >>> * groovy-3.0.0-SNAPSHOT/groovy-raw-3.0.0-SNAPSHOT.jar >>> * groovy-3.0.0-SNAPSHOT/lib/groovy-raw-3.0.0-SNAPSHOT.jar -- >>> corrected >>> as the absolute path >>> * groovy-3.0.0-SNAPSHOT/lib/groovy-raw-3.0.0-SNAPSHOT.jar -- >>> corrected >>> as the absolute path >>> >>> >>> >>> >>> -- >>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >>> >> >> >