You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Sam Corbett <sa...@cloudsoft.io> on 2018/11/27 17:46:21 UTC
Re: build error question
I also observe this test failure.
git bisect indicates that it was introduced by commit
fdc7d82f6d69d3db956b805e45ec57707709dd5d [1], which simply changed the
value of the `felix.framework.version` pom property from 5.6.1 to 5.6.10.
My environment:
$ mvn -version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T19:41:47+01:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 1.8.0_121, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.1", arch: "x86_64", family: "mac"
[1]
https://github.com/apache/brooklyn-server/commit/fdc7d82f6d69d3db956b805e45ec57707709dd5d
On Wed, 26 Sep 2018 at 23:26, Geoff Macartney <ge...@gmail.com>
wrote:
> Hi all,
>
> Was going to try out Paul's PRs for Java 11, but thought I'd catch up and
> build first with Java 8. This was working for me within the last couple of
> weeks, but now I'm consistently getting a failure
>
>
> testErrorsCaughtByApiAndRestApiWorks(org.apache.brooklyn.launcher.BrooklynLauncherTest)
> Time elapsed: 0.002 sec <<< FAILURE!
>
> java.lang.RuntimeException: java.net.SocketException: Socket closed
>
> at
>
> org.apache.brooklyn.launcher.BrooklynLauncherTest.testErrorsCaughtByApiAndRestApiWorks(BrooklynLauncherTest.java:286)
>
> Caused by: java.net.SocketException: Socket closed
>
> at
>
> org.apache.brooklyn.launcher.BrooklynLauncherTest.testErrorsCaughtByApiAndRestApiWorks(BrooklynLauncherTest.java:286)
>
>
>
> This is building with java version "1.8.0_181" on OSX 10.13.6. Does anyone
> do that any more, or is everyone building using Docker? Has anyone else
> seen the above?
>
>
> Best
>
> Geoff
>
Re: build error question
Posted by Geoff Macartney <ge...@gmail.com>.
Hm, that's a pity - nothing obvious as to what the cause, or fix, is. Is
anyone consistently *not* seeing this? (Paul, I guess.) It seems like
something you'd have expected to cause more problems than it has so perhaps
it's only occurring in some people's builds.
G
On Tue, 27 Nov 2018 at 17:46 Sam Corbett <sa...@cloudsoft.io> wrote:
> I also observe this test failure.
>
> git bisect indicates that it was introduced by commit
> fdc7d82f6d69d3db956b805e45ec57707709dd5d [1], which simply changed the
> value of the `felix.framework.version` pom property from 5.6.1 to 5.6.10.
>
> My environment:
>
> $ mvn -version
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
> 2018-10-24T19:41:47+01:00)
> Maven home: /usr/local/Cellar/maven/3.6.0/libexec
> Java version: 1.8.0_121, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "10.14.1", arch: "x86_64", family: "mac"
>
> [1]
>
> https://github.com/apache/brooklyn-server/commit/fdc7d82f6d69d3db956b805e45ec57707709dd5d
>
> On Wed, 26 Sep 2018 at 23:26, Geoff Macartney <ge...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > Was going to try out Paul's PRs for Java 11, but thought I'd catch up and
> > build first with Java 8. This was working for me within the last couple
> of
> > weeks, but now I'm consistently getting a failure
> >
> >
> >
> testErrorsCaughtByApiAndRestApiWorks(org.apache.brooklyn.launcher.BrooklynLauncherTest)
> > Time elapsed: 0.002 sec <<< FAILURE!
> >
> > java.lang.RuntimeException: java.net.SocketException: Socket closed
> >
> > at
> >
> >
> org.apache.brooklyn.launcher.BrooklynLauncherTest.testErrorsCaughtByApiAndRestApiWorks(BrooklynLauncherTest.java:286)
> >
> > Caused by: java.net.SocketException: Socket closed
> >
> > at
> >
> >
> org.apache.brooklyn.launcher.BrooklynLauncherTest.testErrorsCaughtByApiAndRestApiWorks(BrooklynLauncherTest.java:286)
> >
> >
> >
> > This is building with java version "1.8.0_181" on OSX 10.13.6. Does
> anyone
> > do that any more, or is everyone building using Docker? Has anyone else
> > seen the above?
> >
> >
> > Best
> >
> > Geoff
> >
>