Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21905

intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None

      Since approximately 1/30 we have seen 15 very intermittent archiving failures in Jenkins, of the form:

      Archiving artifacts
ERROR: Failed to archive artifacts: versions/**, archive/**
java.io.IOException: Failed to extract /foo/bar/slave/workspace/someJob/transfer of 7 files
	at hudson.FilePath.readFromTar(FilePath.java:2088)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:2000)
	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705)
	at hudson.model.Run.execute(Run.java:1695)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: java.io.EOFException: Unexpected end of ZLIB input stream
	at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186)
	at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106)
	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
	at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)
	at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)
	at hudson.FilePath.readFromTar(FilePath.java:2066)
	... 12 more
Build step 'Archive the artifacts' changed build result to FAILURE

      We definitely have seen this running 1.548 and later, especially with 1.549. I cannot confirm if we saw it with 1.547 or earlier, but if so, I think it was less frequent. It seems to be a relatively new issue we are seeing.

            olivergondza Oliver Gondža
            sroth Steve Roth
            Votes:
            10 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated:
              Resolved: