[llvm-dev] Buildbots building one revision at a time

Michael Kruse via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 25 12:14:44 PST 2021


Am Mi., 24. Feb. 2021 um 17:55 Uhr schrieb Galina Kistanova via
llvm-dev <llvm-dev at lists.llvm.org>:
> Every worker owner has permissions to control the worker itself and the queue of the build requests, modulo to unknown issues. If the worker owners logged in and the github accounts, they logged in with, have e-mail addresses matching those in the workers info. Yours must be powerllvm at ca.ibm.com.

That's a good thing to know. I tried this myself and added
pollybot at meinersbur.de to GitHub's list of my email addresses. After
logging in with GitHub, it unfortunately does not work. Any action I
try is denied with a "unable to pause worker
polly-x86_64-fdcserver:you need to have role 'LLVM Lab team'" message.

The problem that I currently have is that one of my buildbots
(https://lab.llvm.org/staging/#/workers/19) live-locks after a few
hours. The master thinks ithe worker is still building, but the worker
is doing nothing. It's twisted.log says

2021-02-24 04:27:04-0600 [-] WorkerForBuilder.commandComplete
<buildbot_worker.commands.shell.WorkerShellCommand object at
0x7f59b68def10>
2021-02-24 04:33:24-0600 [-] sending app-level keepalive
2021-02-24 04:33:24-0600 [Broker,client] Master replied to keepalive,
everything's fine
2021-02-24 04:43:24-0600 [-] sending app-level keepalive
2021-02-24 04:43:24-0600 [Broker,client] Master replied to keepalive,
everything's fine
[... lots of keepalive entries ...]

I have to restart the buildbot-worker to start working on the next job
only to live-lock again in a few hours. For this reason I put this
worker to staging instead of production. I sthis a known problem?

Michael


More information about the llvm-dev mailing list