Paul suggested that I use a directory with a space in it, and indeed, my build works fine now: https://scans.gradle.com/s/4srwbfihneszm
So it seems a couple of our tests don't tolerate spaces in paths... Anyhow, otherwise, it works, so... +1 (binding) Guillaume On Fri, Dec 21, 2018 at 10:12 AM Guillaume Laforge <glafo...@gmail.com> wrote: > My build scan FYI > https://scans.gradle.com/s/xhbwibzr453hs > > On Fri, Dec 21, 2018 at 9:57 AM Guillaume Laforge <glafo...@gmail.com> > wrote: > >> When building from sources (from my new laptop), I'm seeing two test >> failures: >> >> groovy.security.SecurityTest > testConstructorBug FAILED >> junit.framework.AssertionFailedError: Security test was expected to >> run successfully, but failed (results on System.out) >> at junit.framework.Assert.fail(Assert.java:57) >> at junit.framework.TestCase.fail(TestCase.java:227) >> at >> groovy.security.SecurityTestSupport.executeTest(SecurityTestSupport.java:228) >> at >> groovy.security.SecurityTestSupport.parseAndExecute(SecurityTestSupport.java:208) >> at >> groovy.security.SecurityTestSupport.access$200(SecurityTestSupport.java:46) >> at >> groovy.security.SecurityTestSupport$4.run(SecurityTestSupport.java:289) >> at >> groovy.security.SecurityTestSupport$4.run(SecurityTestSupport.java:280) >> at java.security.AccessController.doPrivileged(Native Method) >> at >> groovy.security.SecurityTestSupport.assertExecute(SecurityTestSupport.java:280) >> at >> groovy.security.SecurityTest.testConstructorBug(SecurityTest.java:96) >> >> groovy.lang.ClassReloadingTest > testReloading FAILED >> Assertion failed: >> >> assert "goodbye" == message >> | | >> | 'hello' >> false >> at >> org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:415) >> at >> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:672) >> at >> groovy.lang.ClassReloadingTest.testReloading(ClassReloadingTest.groovy:60) >> >> >> On Fri, Dec 21, 2018 at 1:28 AM Paul King <pa...@asert.com.au> wrote: >> >>> >>> Dear development community, >>> >>> I am happy to start the VOTE thread for a Groovy 2.5.5 release! >>> >>> This release includes 20 bug fixes/improvements as outlined in the >>> changelog: >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12344435 >>> >>> Tag: >>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_5 >>> Tag commit id: 5014d858d081ca463d03128e5d6eb2440184f492 >>> >>> The artifacts to be voted on are located as follows (r31631). >>> Source release: >>> https://dist.apache.org/repos/dist/dev/groovy/2.5.5/sources >>> Convenience binaries: >>> https://dist.apache.org/repos/dist/dev/groovy/2.5.5/distribution >>> >>> Release artifacts are signed with a key from the following file: >>> https://dist.apache.org/repos/dist/dev/groovy/KEYS >>> >>> Please vote on releasing this package as Apache Groovy 2.5.5. >>> >>> Reminder on ASF release approval requirements for PMC members: >>> http://www.apache.org/legal/release-policy.html#release-approval >>> Hints on validating checksums/signatures (but replace md5sum with >>> sha256sum): >>> https://www.apache.org/info/verification.html >>> >>> The vote is open for the next 72 hours and passes if a majority of at >>> least three +1 PMC votes are cast. >>> >>> [ ] +1 Release Apache Groovy 2.5.5 >>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >>> [ ] -1 Do not release Apache Groovy 2.5.5 because... >>> >>> Here is my vote: >>> >>> +1 (binding) >>> >>> >> >> -- >> Guillaume Laforge >> Apache Groovy committer & PMC Vice-President >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Twitter: @glaforge <http://twitter.com/glaforge> >> > > > -- > Guillaume Laforge > Apache Groovy committer & PMC Vice-President > Developer Advocate @ Google Cloud Platform > > Blog: http://glaforge.appspot.com/ > Twitter: @glaforge <http://twitter.com/glaforge> > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Twitter: @glaforge <http://twitter.com/glaforge>
