See 
<https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/5134/display/redirect>

Changes:


------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on apache-beam-jenkins-14 (beam) in workspace 
/home/jenkins/jenkins-slave/workspace/beam_Publish_Beam_SDK_Snapshots
The recommended git tool is: NONE
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Using shallow clone with depth 1
Avoid fetching tags
Cloning repository https://github.com/apache/beam.git
 > git init 
 > /home/jenkins/jenkins-slave/workspace/beam_Publish_Beam_SDK_Snapshots/src # 
 > timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git --version # 'git version 2.25.1'
 > git fetch --no-tags --force --progress --depth=1 -- 
 > https://github.com/apache/beam.git +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
FATAL: hudson.remoting.ChannelClosedException: Channel 
"hudson.remoting.Channel@14d53a58:apache-beam-jenkins-14": Remote call on 
apache-beam-jenkins-14 failed. The channel is closing down or has closed down
java.io.IOException
        at hudson.remoting.Channel.close(Channel.java:1470)
        at hudson.remoting.Channel.close(Channel.java:1447)
        at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:902)
        at hudson.slaves.SlaveComputer.access$100(SlaveComputer.java:111)
        at hudson.slaves.SlaveComputer$2.run(SlaveComputer.java:782)
        at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at 
jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused: hudson.remoting.ChannelClosedException: Channel 
"hudson.remoting.Channel@14d53a58:apache-beam-jenkins-14": Remote call on 
apache-beam-jenkins-14 failed. The channel is closing down or has closed down
        at hudson.remoting.Channel.call(Channel.java:993)
        at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
Caused: hudson.remoting.RemotingSystemException
        at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:301)
        at com.sun.proxy.$Proxy129.setRemoteUrl(Unknown Source)
        at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.setRemoteUrl(RemoteGitImpl.java:311)
        at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:990)
        at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1243)
        at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1307)
        at hudson.scm.SCM.checkout(SCM.java:540)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1215)
        at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:645)
        at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85)
        at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:517)
        at hudson.model.Run.execute(Run.java:1896)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
        at hudson.model.ResourceController.execute(ResourceController.java:101)
        at hudson.model.Executor.run(Executor.java:442)
ERROR: apache-beam-jenkins-14 is offline; cannot locate jdk_1.8_latest

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to