I have tested with 10.2.6 and JDK 1.8.0_121 and Maven 3.5.0.

The build hangs after this, i.e., the build does not continue and does not
complete:

Running TestSuite
Configuring TestNG with: TestNG652Configurator
java.lang.Exception: Error
at
org.netbeans.html.json.impl.OnReceiveTest.performErrorJSONCallNoHandling(OnReceiveTest.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
at org.testng.TestNG.run(TestNG.java:1030)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:77)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:189)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:105)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)

Happy to take any further steps or do anything to help.

Gj

On Mon, Oct 9, 2017 at 7:11 AM, Anton Epple <toni.ep...@eppleton.de> wrote:

> Hello Jaroslav,
>
> +1
> I have tested with 10.2.6 and JDK8 u131 and the build succeeds here as
> well.
>
> --Toni
>
>
>
> Am 09.10.17, 05:37 schrieb "Jaroslav Tulach" <jaroslav.tul...@oracle.com>:
>
>     Hello William.
>     Thanks for testing.
>
>     >> William Beebe <wbe...@gmail.com>: 08.10.17 @ 21:27 <<
>     > Downloaded and attempted to execute mvn...
>     >
>     > Failed with...
>     >
>     > Running TestSuite
>     > Configuring TestNG with: TestNG652Configurator
>     > java.lang.Exception: Error
>     > at
>     > org.netbeans.html.json.impl.OnReceiveTest.
> performErrorJSONCallNoHandling(OnR
>     > eceiveTest.java:64) at sun.reflect.NativeMethodAccessorImpl.
> invoke0(Native
>     > Method)
>     > at
>     > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62
>     > ) at
>     > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl
>     > .java:43) at java.lang.reflect.Method.invoke(Method.java:498)
>     > at
>     > org.testng.internal.MethodInvocationHelper.invokeMethod(
> MethodInvocationHelp
>     > er.java:80) at org.testng.internal.Invoker.
> invokeMethod(Invoker.java:715)
>     > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>     > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>     > at
>     > org.testng.internal.TestMethodWorker.invokeTestMethods(
> TestMethodWorker.java
>     > :127) at org.testng.internal.TestMethodWorker.run(
> TestMethodWorker.java:111)
>     > at org.testng.TestRunner.privateRun(TestRunner.java:767)
>     > at org.testng.TestRunner.run(TestRunner.java:617)
>     > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>     > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>     > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>     > at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>     > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>     > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>     > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>     > at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>     > at org.testng.TestNG.run(TestNG.java:1030)
>     > at
>     > org.apache.maven.surefire.testng.TestNGExecutor.run(
> TestNGExecutor.java:77)
>     > at
>     > org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.
> executeMulti(TestN
>     > GDirectoryTestSuite.java:189) at
>     > org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.
> execute(TestNGDire
>     > ctoryTestSuite.java:105) at
>     > org.apache.maven.surefire.testng.TestNGProvider.invoke(
> TestNGProvider.java:1
>     > 17) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     > at
>     > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62
>     > ) at
>     > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl
>     > .java:43) at java.lang.reflect.Method.invoke(Method.java:498)
>     > at
>     > org.apache.maven.surefire.util.ReflectionUtils.
> invokeMethodWithArray2(Reflec
>     > tionUtils.java:208) at
>     > org.apache.maven.surefire.booter.ProviderFactory$
> ProviderProxy.invoke(Provid
>     > erFactory.java:158) at
>     > org.apache.maven.surefire.booter.ProviderFactory.
> invokeProvider(ProviderFact
>     > ory.java:86) at
>     > org.apache.maven.surefire.booter.ForkedBooter.
> runSuitesInProcess(ForkedBoote
>     > r.java:153) at
>     > org.apache.maven.surefire.booter.ForkedBooter.main(
> ForkedBooter.java:95)
>
>     Is that a failure? When running the tests, this exception is printed,
> but then
>     the build continues (on my computer) without issues.
>
>     > This is on macOS 10.13
>
>     I've just tested on my Mac Mini 10.12.6 with Java 1.8.0_102 and Maven
> 3.1.1 -
>     the execution of "mvn install" got through and printed "BUILD
> SUCCESS"  at the
>     end.
>
>     Can you tell me your Java, Maven versions? Maybe there is the
> difference...
>
>     Thanks again for trying.
>     -jt
>
>     > On Sun, Oct 8, 2017 at 7:41 AM, Jaroslav Tulach <
> jaroslav.tul...@oracle.com>
>     > wrote:
>     > > Hi guys,
>     > > I've set a Jenkins job up which can prepare a release bits of
> HTML/Java
>     > > API
>     > > and gives instructions how to build the ZIP file and test it:
>     > >
>     > > https://urldefense.proofpoint.com/v2/url?u=https-3A__builds.
> apache.org_vie
>     > > w_Incubator-2520Projects_job_&d=DwIBaQ&c=
> RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpk
>     > > KY057SbK10&r=tnLz5-vaI8x9g_xBBlFGf_ldS0-TN1M3i9fMP1FPWgk&
> m=YG4xzGgDrcyk2o5
>     > > fHnxRwjW9Yu1nyymXV6ENRKcVVmY&s=B2dDjkQBUc6Z4IgTFyahGz2UuH2Cxh
> 48lxfdtr3Uu3k
>     > > &e= incubator-netbeans-html4j-release/
>     > >
>     > > after a bit of configuration struggling the [build #16](https://
>     > > builds.apache.org/view/Incubator%20Projects/job/
> incubator-netbeans-html4j-
>     > > release/16/) seems to deliver releasable ZIP file:
>     > >
>     > > https://urldefense.proofpoint.com/v2/url?u=https-3A__builds.
> apache.org_vie
>     > > w_Incubator-2520Projects_job_&d=DwIBaQ&c=
> RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpk
>     > > KY057SbK10&r=tnLz5-vaI8x9g_xBBlFGf_ldS0-TN1M3i9fMP1FPWgk&
> m=YG4xzGgDrcyk2o5
>     > > fHnxRwjW9Yu1nyymXV6ENRKcVVmY&s=B2dDjkQBUc6Z4IgTFyahGz2UuH2Cxh
> 48lxfdtr3Uu3k
>     > > &e= incubator-netbeans-html4j-release/16/artifact/
>     > > incubating-netbeans-html4j-1.5.zip
>     > >
>     > > It's md5sum is a45bda33200c208d0d837b0746a7dcce.
>     > >
>     > > I've done the basic testing on Linux, as well as I tried to use the
>     > > version
>     > > 1.5 in Bck2Brwsr VM (works fine) and TeaVM which needed a [bit of
>     > > patching]
>     > > (https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_konsolety
>     > > per_teavm_pull_304&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5Y
> TpkKY057SbK10&
>     > > r=tnLz5-vaI8x9g_xBBlFGf_ldS0-TN1M3i9fMP1FPWgk&m=
> YG4xzGgDrcyk2o5fHnxRwjW9Yu
>     > > 1nyymXV6ENRKcVVmY&s=qa8AASAkNkfgF6EMp76nXhscdy9Md2jL2Vy8wnzpsbU&e=
> ). In
>     > > any case the HTML/Java
>     > > API seems releasable from my point of view.
>     > >
>     > > This is the first attempt to perform Apache release of NetBeans
> HTML/Java
>     > > API.
>     > > As such there are almost no new features. Mostly just licensing
> changes,
>     > > bugfixes and other little tweaks. See Javadoc section about post
> 1.4
>     > > release
>     > > improvements:
>     > >
>     > > https://urldefense.proofpoint.com/v2/url?u=https-3A__builds.
> apache.org_job
>     > > _incubator-2Dnetbeans-2Dhtml4j-2Dlinux_javadoc_&d=
> DwIBaQ&c=RoP1YumCXCgaWHv
>     > > lZYR8PQcxBKCX5YTpkKY057SbK10&r=tnLz5-vaI8x9g_xBBlFGf_ldS0-
> TN1M3i9fMP1FPWgk
>     > > &m=YG4xzGgDrcyk2o5fHnxRwjW9Yu1nyymXV6ENRKcVVmY&s=aE6DiAcwK1P-
> 20ylY9C350umn
>     > > q3CAfyA5vEGMSDv6jA&e=
>     > >
>     > > Please take the ZIP file for a spin and vote to approve the release
>     > > and to request the approval of the Incubator PMC to publish it on
>     > > our site.
>     > >
>     > > Everyone is encouraged to vote, including non-committers.
>     > >
>     > > This vote shall close in the usual 72 hours.
>     > > -jt
>     > >
>     > > PS: I am keeping my fingers crossed, hoping things go well.
>
>
>
>
>
>

Reply via email to