Build failed in Jenkins: java-parent-project-v7-multi » Amazon-11,Windows2016 #1442

[Shibboleth Jenkins]

See <http://127.0.0.1:1583/jenkins/job/java-parent-project-v7-multi/jdk=Amazon-11,label=Windows2016/1442/display/redirect>

Changes:


------------------------------------------
Started by upstream project "java-parent-project-v7-multi" build number 1442
originally caused by:
 Started by upstream project "trigger-multi-v7" build number 151
 originally caused by:
  Started by upstream project "java-identity-provider-v3-nightly" build number 1705
  originally caused by:
   Started by upstream project "java-opensaml-v3-nightly" build number 1704
   originally caused by:
    Started by upstream project "spring-extensions-v5-nightly" build number 1698
    originally caused by:
     Started by upstream project "java-support-v7-nightly" build number 1698
     originally caused by:
      Started by upstream project "java-parent-project-v7-nightly" build number 1693
      originally caused by:
       Started by upstream project "trigger-nightly-v7" build number 1689
       originally caused by:
        Started by timer
Running as SYSTEM
Building remotely on EC2 (WindowsServer2016) - WindowsServer2016 (i-076805d74019662f1) (Windows2016) in workspace c:\opt\jenkins\workspace\java-parent-project-v7-multi\jdk\Amazon-11\label\Windows2016
No credentials specified
Cloning the remote Git repository
Cloning repository git://git.shibboleth.net/java-parent-project
 > git init c:\opt\jenkins\workspace\java-parent-project-v7-multi\jdk\Amazon-11\label\Windows2016 # timeout=10
Fetching upstream changes from git://git.shibboleth.net/java-parent-project
 > git --version # timeout=10
 > git fetch --tags --force --progress -- git://git.shibboleth.net/java-parent-project +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git://git.shibboleth.net/java-parent-project # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git://git.shibboleth.net/java-parent-project # timeout=10
Fetching upstream changes from git://git.shibboleth.net/java-parent-project
 > git fetch --tags --force --progress -- git://git.shibboleth.net/java-parent-project +refs/heads/*:refs/remotes/origin/* # timeout=10
Checking out Revision e88ab1fd7ab96dae76c12e49db7445f831209d15 (refs/remotes/origin/maint-7)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e88ab1fd7ab96dae76c12e49db7445f831209d15 # timeout=10
Commit message: "JPAR-149 - Reinstate checks for missing or misplaced Javadoc"
 > git rev-list --no-walk e88ab1fd7ab96dae76c12e49db7445f831209d15 # timeout=10
[Windows2016] $ cmd.exe /C "\opt\maven_home\bin\mvn.cmd -version && exit %%ERRORLEVEL%%"
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T18:41:47Z)
Maven home: c:\opt\maven_home\bin\..
Java version: 11.0.5, vendor: Amazon.com Inc., runtime: c:\opt\jdk\amazon-11
Default locale: en_US, platform encoding: Cp1252
OS name: "windows server 2016", version: "10.0", arch: "amd64", family: "windows"
[Windows2016] $ cmd.exe /C "\opt\maven_home\bin\mvn.cmd -Djdk=Amazon-11 -Dmatrix-combinations= -Dlabel=Windows2016 -B clean test -Prelease --update-snapshots --fail-at-end && exit %%ERRORLEVEL%%"
[INFO] Scanning for projects...
[WARNING] The project net.shibboleth:parent:pom:7.11.1-SNAPSHOT uses prerequisites which is only intended for maven-plugin projects but not for non maven-plugin projects. For such purposes you should use the maven-enforcer-plugin. See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
[INFO] 
[INFO] -----------------------< net.shibboleth:parent >------------------------
[INFO] Building Shibboleth Project V3 Super POM 7.11.1-SNAPSHOT
[INFO] --------------------------------[ pom ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ parent ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  5.893 s
[INFO] Finished at: 2019-12-20T02:46:09Z
[INFO] ------------------------------------------------------------------------
FATAL: java.io.IOException: Pipe is already closed
hudson.remoting.FastPipedInputStream$ClosedBy: The pipe was closed at...
	at hudson.remoting.FastPipedOutputStream.error(FastPipedOutputStream.java:100)
	at hudson.remoting.FastPipedOutputStream.close(FastPipedOutputStream.java:90)
	at hudson.plugins.ec2.util.Closeables.closeQuietly(Closeables.java:23)
	at hudson.plugins.ec2.win.winrm.WindowsProcess$2.run(WindowsProcess.java:146)
Caused: java.io.IOException: Pipe is already closed
	at hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:154)
	at hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:138)
	at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:89)
	at hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:62)
	at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:46)
	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:47)
	at hudson.remoting.Channel.send(Channel.java:723)
	at hudson.remoting.Channel.close(Channel.java:1438)
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (WindowsServer2016) - WindowsServer2016 (i-076805d74019662f1)
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
		at hudson.remoting.Request.call(Request.java:202)
		at hudson.remoting.Channel.call(Channel.java:956)
		at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1086)
		at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510)
		at hudson.model.Run.execute(Run.java:1816)
		at hudson.matrix.MatrixRun.run(MatrixRun.java:153)
		at hudson.model.ResourceController.execute(ResourceController.java:97)
		at hudson.model.Executor.run(Executor.java:429)
Caused: hudson.remoting.RequestAbortedException
	at hudson.remoting.Request.abort(Request.java:340)
	at hudson.remoting.Channel.terminate(Channel.java:1040)
	at hudson.remoting.Channel.close(Channel.java:1446)
	at hudson.remoting.Channel.close(Channel.java:1405)
	at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:847)
	at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:108)
	at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:756)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
ERROR: Step ‘Publish TestNG Results’ failed: no workspace for java-parent-project-v7-multi/jdk=Amazon-11,label=Windows2016 #1442
ERROR: EC2 (WindowsServer2016) - WindowsServer2016 (i-076805d74019662f1) is offline; cannot locate Amazon-11