[ 
https://issues.apache.org/jira/browse/BEAM-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863517#comment-16863517
 ] 

Luke Cwik commented on BEAM-7532:
---------------------------------

The failure seems to now occur during buildDockerImage 
([https://builds.apache.org/job/beam_PostCommit_Website_Test/582/console]):
{code:java}
15:05:33 > Task :website:buildDockerImage
15:05:33 Sending build context to Docker daemon  27.14MB
15:05:33 
15:05:33 Step 1/7 : FROM ruby:2.5
15:05:33  ---> 80f53b90f865
15:05:33 Step 2/7 : WORKDIR /ruby
15:05:33  ---> Using cache
15:05:33  ---> c0b25c9d63e5
15:05:33 Step 3/7 : RUN gem install bundler
15:05:33  ---> Running in 0d16b97b63cb
15:05:33 Successfully installed bundler-2.0.2
15:05:33 1 gem installed
15:35:20 Build timed out (after 30 minutes). Marking the build as aborted.
15:35:20 Build was aborted
15:35:20 
15:35:20 > Task :website:buildDockerImage FAILED
15:35:20 The message received from the daemon indicates that the daemon has 
disappeared.
15:35:20 Build request sent: Build{id=921d4e14-1095-4280-81c6-d57cc8e2f326, 
currentDir=/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Website_Test/src}
15:35:20 Attempting to read last messages from the daemon log...
15:35:20 Daemon pid: 31849
15:35:20   log file: /home/jenkins/.gradle/daemon/5.2.1/daemon-31849.out.log
15:35:20 ----- Last  20 lines from daemon log file - daemon-31849.out.log -----
15:35:20 22:05:22.469 [INFO] 
[org.gradle.launcher.daemon.server.exec.ForwardClientInput] The daemon will no 
longer process any standard input.
15:35:20 22:05:22.470 [DEBUG] 
[org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon] 
Requesting daemon stop after processing 
Build{id=921d4e14-1095-4280-81c6-d57cc8e2f326, 
currentDir=/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Website_Test/src}
15:35:20 22:05:22.470 [LIFECYCLE] 
[org.gradle.launcher.daemon.server.DaemonStateCoordinator] Daemon will be 
stopped at the end of the build stopping after processing
15:35:20 22:05:22.470 [DEBUG] 
[org.gradle.launcher.daemon.server.DaemonStateCoordinator] Stop as soon as idle 
requested. The daemon is busy: true
15:35:20 22:05:22.470 [DEBUG] 
[org.gradle.launcher.daemon.server.DaemonStateCoordinator] daemon stop has been 
requested. Sleeping until state changes.
15:35:20 22:05:22.474 [DEBUG] 
[org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has started 
executing the build.
15:35:20 22:05:22.474 [DEBUG] 
[org.gradle.launcher.daemon.server.exec.ExecuteBuild] Executing build with 
daemon context: 
DefaultDaemonContext[uid=ca8d6458-493a-4a73-844c-c8b322de2cfc,javaHome=/usr/local/asfpackages/java/jdk1.8.0_191,daemonRegistryDir=/home/jenkins/.gradle/daemon,pid=31849,idleTimeout=120000,priority=NORMAL,daemonOpts=-Xmx4g,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]
15:35:20 Configuration on demand is an incubating feature.
15:35:20 Sending build context to Docker daemon  27.14MB
{code}

> Beam Website Publish workflow is consistently timing out since last week. 
> --------------------------------------------------------------------------
>
>                 Key: BEAM-7532
>                 URL: https://issues.apache.org/jira/browse/BEAM-7532
>             Project: Beam
>          Issue Type: Bug
>          Components: website
>            Reporter: Valentyn Tymofieiev
>            Assignee: Udi Meiri
>            Priority: Major
>
> https://builds.apache.org/job/beam_PostCommit_Website_Publish/2868/console
> {noformat}
> 09:50:57 > Task :website:createDockerContainer
> 09:50:58 
> 09:50:58 > Task :website:startDockerContainer
> 09:50:58 71b54f49f9766072cae5130debe4eb71088226929c62ad42b4bef7df99b48a7e
> 09:51:28 
> 09:51:28 > Task :website:setupDockerContainer
> 10:20:45 Build timed out (after 30 minutes). Marking the build as aborted.
> 10:20:45 Build was aborted
> 10:20:45 > Task :website:setupDockerContainer FAILED
> {noformat}
> Hi [~alanmyrvold], do you think you could help triage this?
> Thank you!
>  
> cc: [~kenn] [~altay] [~lcwik] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to