this branch should be fixed now as well It was failing on Jenkins ASF as again we hit a bug fixed in OpenJdk but not reported in OracleJdk... (I simply disabled the test) We are back to the famous "It works on my machine" :)
Do we really want to use OracleJdk as a source of truth??? On Wed, 11 Mar 2020 at 18:19, Olivier Lamy <[email protected]> wrote: > ok the branch MJAVADOC-610 has been created from a old master some code > was missing especially some fixes regarding it test (guava apidocs > relocation for MJAVADOC-555_link..) > > On Wed, 11 Mar 2020 at 09:56, Olivier Lamy <[email protected]> wrote: > >> Thanks Robert >> Anyway as the build only fail for jdk7 with mvn 3.2.5 on a particular >> node of the asf machines. >> I build that perfectly with same jdk/mvn.... >> So we cannot really consider this as blocker... >> >> >> On Wed, 11 Mar 2020 at 05:14, Robert Scholte <[email protected]> >> wrote: >> >>> I think I found the root cause. Give me some time to fix this with INFRA >>> On 10-3-2020 12:23:34, Elliotte Rusty Harold <[email protected]> wrote: >>> This is from Jenkins: >>> >>> [INFO] ------------------------------------------------- >>> [INFO] Build Summary: >>> [INFO] Passed: 51, Failed: 1, Errors: 0, Skipped: 18 >>> [INFO] ------------------------------------------------- >>> [ERROR] The following builds failed: >>> [ERROR] * MJAVADOC-338_downloadSources/pom.xml >>> [INFO] ------------------------------------------------- >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 16:41 min >>> [INFO] Finished at: 2020-03-10T00:33:17+00:00 >>> [INFO] Final Memory: 61M/1685M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] [jenkins-event-spy] Generated >>> /home/jenkins/jenkins-slave/workspace/_box_maven-javadoc-plugin_master@2 >>> @tmp/withMaven3b7359f7/maven-spy-20200310-001635-6314901836286016347811.log >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-invoker-plugin:3.2.1:verify >>> (integration-test) on project maven-javadoc-plugin: 1 build failed. >>> See console output above for details. -> [Help 1] >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>> execute goal org.apache.maven.plugins:maven-invoker-plugin:3.2.1:verify >>> (integration-test) on project maven-javadoc-plugin: 1 build failed. >>> See console output above for details. >>> at >>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) >>> at >>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >>> at or >>> >>> On Tue, Mar 10, 2020 at 7:20 AM Elliotte Rusty Harold >>> wrote: >>> > >>> > I'll see if I can dig up some more logs on this. In the meantime as >>> > Robert pointed out, the CI for this plugin is broken/red: >>> > >>> > https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/ >>> > >>> > IMHO, getting that to blue is a prerequisite for a release. This >>> > plugin is not currently in a releasable state.. I am (non-binding) -1 >>> > on this release. >>> > >>> > On Mon, Mar 9, 2020 at 11:15 PM Olivier Lamy wrote: >>> > > >>> > > Hi >>> > > The stack trace is truncated in your email. >>> > > Can you paste the logs to a gist so I can try looking at it. >>> > > There are some old flaky tests relying on having an internet >>> connection. >>> > > But I don't want to fix this now.. >>> > > Actually I need a release for the jetty project which is a bit >>> stucked to >>> > > release jetty 10 as jetty 10 cannot build an aggregated javadoc ATM >>> because >>> > > of some bugs here. >>> > > >>> > > >>> > > On Mon, 9 Mar 2020 at 22:02, Elliotte Rusty Harold >>> > > wrote: >>> > > >>> > > > I see two test failures locally: >>> > > > >>> > > > [ERROR] Failures: >>> > > > [ERROR] JavadocJarTest.testContinueIfFailOnErrorIsFalse:170 >>> > > > [ERROR] JavadocReportTest.testNewline:880 Doesn't handle correctly >>> > > > newline for string parameters. See options and packages files. >>> > > > [ERROR] Errors: >>> > > > [ERROR] >>> > > > >>> FixJavadocMojoTest.testFix:123->executeMojoAndTest:576->invokeCompileGoal:629 >>> > > > » NullPointer >>> > > > [ERROR] JavadocJarTest.testDefaultConfig:77 » MojoExecution >>> > > > MavenReportException: Erro... >>> > > > [ERROR] >>> > > > >>> JavadocJarTest.testIncludeMavenDescriptorWhenExplicitlyConfigured:178 >>> > > > » MojoExecution >>> > > > [ERROR] JavadocJarTest.testInvalidDestdir:152 » MojoExecution >>> > > > MavenReportException: Er... >>> > > > [ERROR] JavadocReportTest.testCustomConfiguration:396 » >>> > > > MojoExecution An error has occ... >>> > > > [ERROR] JavadocReportTest.testDefaultConfiguration:243 » >>> > > > MojoExecution An error has oc... >>> > > > [ERROR] JavadocReportTest.testDocfiles:369 » MojoExecution An error >>> > > > has occurred in Ja... >>> > > > [ERROR] JavadocReportTest.testDoclets:490 » MojoExecution An error >>> > > > has occurred in Jav... >>> > > > [ERROR] JavadocReportTest.testOptionsUmlautEncoding:566 » >>> > > > MojoExecution An error has o... >>> > > > [ERROR] JavadocReportTest.testQuotedPath:532 » MojoExecution An >>> > > > error has occurred in ... >>> > > > [ERROR] JavadocReportTest.testStylesheetfile:1251 » MojoExecution >>> An >>> > > > error has occurre... >>> > > > [ERROR] JavadocReportTest.testSubpackages:320 » MojoExecution An >>> > > > error has occurred in... >>> > > > [ERROR] JavadocReportTest.testToFindJavadoc:735 » MojoExecution An >>> > > > error has occurred ... >>> > > > [INFO] >>> > > > [ERROR] Tests run: 67, Failures: 2, Errors: 13, Skipped: 0 >>> > > > >>> > > > >>> > > > On Mon, Mar 9, 2020 at 2:26 AM Olivier Lamy wrote: >>> > > > > >>> > > > > Hi >>> > > > > I'd like to make a javadoc plugin release. >>> > > > > 2 issues left ATM but I can move them to next version. >>> > > > > >>> > > > > Cheers >>> > > > > -- >>> > > > > Olivier >>> > > > >>> > > > >>> > > > >>> > > > -- >>> > > > Elliotte Rusty Harold >>> > > > [email protected] >>> > > > >>> > > > >>> --------------------------------------------------------------------- >>> > > > To unsubscribe, e-mail: [email protected] >>> > > > For additional commands, e-mail: [email protected] >>> > > > >>> > > > >>> > > >>> > > -- >>> > > Olivier Lamy >>> > > http://twitter.com/olamy | http://linkedin.com/in/olamy >>> > >>> > >>> > >>> > -- >>> > Elliotte Rusty Harold >>> > [email protected] >>> >>> >>> >>> -- >>> Elliotte Rusty Harold >>> [email protected] >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> -- >> Olivier Lamy >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
