New issue
Advanced search Search tips

Issue 616148 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

build109-m2 is offline

Project Member Reported by yunlian@chromium.org, May 31 2016

Issue description

Cc: -sergeybe...@chromium.org

Comment 2 by d...@chromium.org, May 31 2016

Owner: d...@chromium.org
Status: Fixed (was: Untriaged)
chrome-bot@build109-m2:~$ uptime
 10:56:42 up 21 days, 21:08,  1 user,  load average: 0.08, 0.03, 0.05

from twist.log:

2016-05-09 11:29:44-0700 [Broker,client] slave shutting down on command from master
2016-05-09 11:29:44-0700 [Broker,client] lost remote
2016-05-09 11:29:44-0700 [Broker,client] Lost connection to master2.golo.chromium.org:8126
2016-05-09 11:29:44-0700 [Broker,client] Stopping factory <buildslave.bot.BotFactory instance at 0x66da0e0>
2016-05-09 11:29:44-0700 [-] Main loop terminated.
2016-05-09 11:29:44-0700 [-] Server Shut Down.

Restarted the buildslave process.

Comment 3 by d...@chromium.org, May 31 2016

Components: Infra>Labs
Status: Assigned (was: Fixed)
From https://uberchromegw.corp.google.com/i/chromeos/builders/llvm-next-toolchain-group
This buildbot is still offline.

Comment 5 by d...@chromium.org, Jun 2 2016

Status: Fixed (was: Assigned)
Restarted the build slave process, yet again. Same issue as before in #2:

2016-05-31 11:19:16-0700 [-] command finished with signal None, exit code 1, elapsedTime: 1321.855349
2016-05-31 11:19:16-0700 [-] SlaveBuilder.commandComplete <buildslave.commands.shell.SlaveShellCommand instance at 0x76fd3f8>
2016-05-31 11:21:09-0700 [Broker,client] slave shutting down on command from master
2016-05-31 11:21:09-0700 [Broker,client] lost remote
2016-05-31 11:21:09-0700 [Broker,client] Lost connection to master2.golo.chromium.org:8126
2016-05-31 11:21:09-0700 [Broker,client] Stopping factory <buildslave.bot.BotFactory instance at 0x73bbfc8>
2016-05-31 11:21:09-0700 [-] Main loop terminated.
2016-05-31 11:21:09-0700 [-] Server Shut Down.

Sign in to add a comment