Re: progress on executing tests with JDK9 status update

In that case sorry for the misinformation. Sorry I won't have time to look at the last failing test. On Thursday, September 8, 2016, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > On Wed, Sep 7, 2016 at 11:55 AM, Jochen Theodorou > wrote: > >> On 07.09.2016 19:54, John Wagenleitner wr

Re: progress on executing tests with JDK9 status update

On Wed, Sep 7, 2016 at 11:55 AM, Jochen Theodorou wrote: > On 07.09.2016 19:54, John Wagenleitner wrote: > >> On Wed, Sep 7, 2016 at 8:50 AM, Jochen Theodorou > > wrote: >> >> >> >> On 07.09.2016 14:33, Thibault Kruse wrote: >> >> The groovysh tests failed la

Re: progress on executing tests with JDK9 status update

On 07.09.2016 19:54, John Wagenleitner wrote: On Wed, Sep 7, 2016 at 8:50 AM, Jochen Theodorou mailto:blackd...@gmx.org>> wrote: On 07.09.2016 14:33, Thibault Kruse wrote: The groovysh tests failed last because the strategy to read package contents via the ClassLoader does

Re: progress on executing tests with JDK9 status update

On Wed, Sep 7, 2016 at 8:50 AM, Jochen Theodorou wrote: > > > On 07.09.2016 14:33, Thibault Kruse wrote: > >> The groovysh tests failed last because the strategy to read package >> contents via the ClassLoader does not work with Java8. Possibly >> checking how the new Java REPL does things could

Re: progress on executing tests with JDK9 status update

On 07.09.2016 14:33, Thibault Kruse wrote: The groovysh tests failed last because the strategy to read package contents via the ClassLoader does not work with Java8. Possibly checking how the new Java REPL does things could reveal a solution, if they do have tab completion for imports. In the m

Re: progress on executing tests with JDK9 status update

The groovysh tests failed last because the strategy to read package contents via the ClassLoader does not work with Java8. Possibly checking how the new Java REPL does things could reveal a solution, if they do have tab completion for imports. In the meantime, I'd suggest skipping those tests when

Re: progress on executing tests with JDK9 status update

Great progress! Le mardi 6 septembre 2016, Jochen Theodorou a écrit : > Another update on JDK9... > > I now managed to make the last groovy-core tests running! I used > jigsaw-132 for the test. > > Doing a full Groovy build, the only part missing now is the tests in > groovysh. There org.codehau

Re: progress on executing tests with JDK9 status update

Another update on JDK9... I now managed to make the last groovy-core tests running! I used jigsaw-132 for the test. Doing a full Groovy build, the only part missing now is the tests in groovysh. There org.codehaus.groovy.tools.shell.util.PackageHelperImplTest multiple times and I have not y

Re: progress on executing tests with JDK9 status update

On Thu, Aug 25, 2016 at 7:57 AM, John Wagenleitner < john.wagenleit...@gmail.com> wrote: > > On Wed, Aug 24, 2016 at 10:29 PM, Jochen Theodorou > wrote: > >> On 25.08.2016 01:14, John Wagenleitner wrote: >> [...] >> >>> groovy.transform.stc.GenericsSTCTest > testGenericField FAILED >>>

Re: progress on executing tests with JDK9 status update

On Wed, Aug 24, 2016 at 10:29 PM, Jochen Theodorou wrote: > On 25.08.2016 01:14, John Wagenleitner wrote: > [...] > >> groovy.transform.stc.GenericsSTCTest > testGenericField FAILED >> org.codehaus.groovy.control.Mu >> ltipleCompilati

Re: progress on executing tests with JDK9 status update

On 25.08.2016 01:14, John Wagenleitner wrote: [...] groovy.transform.stc.GenericsSTCTest > testGenericField FAILED org.codehaus.groovy.control.Mu ltipleCompilationErrorsException: startup failed: TestScripttestGen

Re: progress on executing tests with JDK9 status update

On Wed, Aug 24, 2016 at 2:32 PM, Jochen Theodorou wrote: > Hi all, > > I made two more tests pass with JDK9 and we are now down to 8 failures in > groovy-core. > > gls.innerClass.InnerClassTest > testThisReferenceForAICInOpenBlock FAILED >> groovy.lang.MissingMethodException: No signature of