Hans Brende created ANY23-370:
---------------------------------
Summary: Jenkins builds are timing out
Key: ANY23-370
URL: https://issues.apache.org/jira/browse/ANY23-370
Project: Apache Any23
Issue Type: Bug
Components: CIS (Jenkins)
Affects Versions: 2.3
Reporter: Hans Brende
Fix For: 2.3
Jenkins builds (e.g., [#1597|https://builds.apache.org/job/Any23-trunk/1597/])
have been sporadically timing out after 120 minutes during the *archival
process*, even though the actual *build process* completes successfully in less
than half an hour. I believe that this is due to the following error:
{noformat}
ERROR: Failed to archive
{org.apache.any23/apache-any23-service/2.3-SNAPSHOT/apache-any23-service-2.3-SNAPSHOT.pom=pom.xml,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48.war=target/apache-any23-service-2.3-SNAPSHOT.war,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.war=target/apache-any23-service-2.3-SNAPSHOT-without-deps.war,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-with-deps.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-with-deps.tar.gz,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-with-deps.zip=target/apache-any23-service-2.3-SNAPSHOT-with-deps.zip,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-without-deps.tar.gz,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-without-deps.zip=target/apache-any23-service-2.3-SNAPSHOT-without-deps.zip,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-server-embedded.tar.gz=target/apache-any23-service-2.3-SNAPSHOT-server-embedded.tar.gz,
org.apache.any23/apache-any23-service/2.3-20180718.234115-48/apache-any23-service-2.3-20180718.234115-48-server-embedded.zip=target/apache-any23-service-2.3-SNAPSHOT-server-embedded.zip}
due to internal error; falling back to full archiving
java.lang.IllegalStateException: End of stream while reading number
at jsync.protocol.BaseReader.readLong(BaseReader.java:40)
at jsync.protocol.BaseReader.readInt(BaseReader.java:26)
at jsync.protocol.ChangeStreamReader.next(ChangeStreamReader.java:54)
at jsync.protocol.ChangeInputStream.next(ChangeInputStream.java:27)
at jsync.protocol.ChangeInputStream.read(ChangeInputStream.java:71)
at
com.cloudbees.jenkins.plugins.jsync.archiver.MD5DigestingInputStream.read(MD5DigestingInputStream.java:39)
at com.google.common.io.LimitInputStream.read(LimitInputStream.java:79)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at com.google.common.io.ByteStreams.copy(ByteStreams.java:193)
at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:35)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:158)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:76)
at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:512)
at
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:881)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429){noformat}
Then, at some point during the *"full archiving"* process, we get the following
message:
{quote}
*Build timed out (after 120 minutes). Marking the build as aborted.*
{quote}
In order to mitigate this timeout error, I've temporarily increased the timeout
to 180 minutes. But this should not be necessary: we should try to fix the
underlying issue. [~lewismc] any idea what's going on here?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
