boris ivan commented on Bug JENKINS-21913

Occurred again today with build 1.553.

Interestingly, while I see the same stack trace later in the build as described above, I do notice some odd output slightly earlier than the stack trace.

The Maven goals this is executing are: integration-test site site:deploy

When executing the maven goal "site", it generates javadocs and a few other standard reports. It looks like it is progressing along, and then I see the following strange output below:

08:35:17 Constructing Javadoc information...
08:35:17 Standard Doclet version 1.7.0_40
08:35:17 Building tree for all the packages and classes...
...
...
08:35:17 200 warnings
08:35:17 [WARNING] Javadoc Warnings
08:35:17 [WARNING] C:\Jenkins\workspace[redacted].java:27: warning - @count is an unknown tag.
08:35:17 [WARNING] C:\Jenkins\workspace[redacted].java:27: warning - @volname is an unknown tag.
08:35:17 [WARNING] C:\Jenkins\workspace[redacted].java:80: warning - @return tag has no arguments.
08:35:17 [8mha:AAAAYx+LCAAAAAAAAP9b85aBtbiIQSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvll6S2fNly5fzGzauYGBgqihikoFqS8/OK83NS9ZwhNEghAwQwghQWAACwxA+XYgAAAA== [0m[WARNING] C:\Jenkins\workspace[redacted].java:80: warning - @param argument "hostIP" is not a parameter name.

Note the garbage above "8mha:AAAAYx+LCAAA......."

Next, the site is deployed to an external web server (site:deploy).

After this, the 'maven' portion of the build is complete, and the email-ext plugin would normally fire. But this is what I see instead:

08:36:56 ERROR: Failed to parse POMs
08:36:56 hudson.remoting.ChannelClosedException: channel is already closed
08:36:56 at hudson.remoting.Channel.send(Channel.java:524)
08:36:56 at hudson.remoting.Request.call(Request.java:129)
08:36:56 at hudson.remoting.Channel.call(Channel.java:722)
08:36:56 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
08:36:56 at com.sun.proxy.$Proxy74.isAlive(Unknown Source)
08:36:56 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:930)
08:36:56 at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:165)
08:36:56 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:833)
08:36:56 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585)
08:36:56 at hudson.model.Run.execute(Run.java:1676)
08:36:56 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
08:36:56 at hudson.model.ResourceController.execute(ResourceController.java:88)
08:36:56 at hudson.model.Executor.run(Executor.java:231)
08:36:56 Caused by: hudson.remoting.DiagnosedStreamCorruptionException
08:36:56 Read back: 'o'
08:36:56 Read ahead: '[redacted].html#108">108</a></td></tr>' 0x0d 0x0a
08:36:56 '<tr class="b">' 0x0d 0x0a
08:36:56 '<td><img alt="Errors" src="" /></td>' 0x0d 0x0a
08:36:56 '<td>Line is longer than 80 characters (found 82).</td>' 0x0d 0x0a

Note the last line above. "Line is longer than 80 characters". That is something specific to the checkstyle reports, during the Maven "site" goal (I think). Hmm.....

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to