e
On Sat, 5 Oct 2019 at 17:01, Ken Cunningham wrote:
>
>> If I run it manually then it works as expected.
>
> Permissions issue, maybe with pid file?
On the good side: the exact same configuration works on 10.6, so no
clue why it doesn't on 10.13.
But the folder is owned by buildbot, the pid
> If I run it manually then it works as expected.
Permissions issue, maybe with pid file?
K
On Wed, 2 Oct 2019 at 03:30, Joshua Root wrote:
> On 2019-10-2 11:19 , Mojca Miklavec wrote:
> > sudo launchctl load -w
> > /Library/LaunchDaemons/org.macports.buildworker.name.plist
> > sudo launchctl start org.macports.buildworker.name
> >
> > But I keep getting the following error in
On 2019-10-2 11:19 , Mojca Miklavec wrote:
> sudo launchctl load -w
> /Library/LaunchDaemons/org.macports.buildworker.name.plist
> sudo launchctl start org.macports.buildworker.name
>
> But I keep getting the following error in /var/log/system.log
>
> Service exited with abnormal code: 1
>
Hi,
I tested buildbot-worker quite a bit, but maybe / apparently never
with launchctl.
The part that I don't quite understand is the following:
* I've been running buildbot-slave 0.8 for a few years as a
LaunchDeamon without any issues.
* I now tried to upgrade the setup to buildbot-worker 2.
