On Mon, Oct 10, 2016 at 06:46:50PM +, Holger Levsen wrote:
> and now also been added back to the build network, with 3 new builder
> jobs for a total of 60 (running on a total of 20 armhf boards).
^ 22 armhf board is
correct :) (+sorry for the
Hey,
On Wed, Oct 05, 2016 at 08:42:17PM -0700, Vagrant Cascadian wrote:
> opi2a is back!
and now also been added back to the build network, with 3 new builder
jobs for a total of 60 (running on a total of 20 armhf boards).
Not sure how to rearrange build jobs off the top of my
> For some
On Wed 2016-10-05 23:42:17 -0400, Vagrant Cascadian wrote:
> The whole ordeal did trigger a thought about adding init system
> variations to the builds... at least could do systemd and sysvinit at
> the moment without a *huge* amount of trouble, unless we're relying on
> some init-specific
opi2a is back! Not sure how to rearrange build jobs off the top of my
head, but we've got several cores just sittle idle again. :)
For some reason, systemd wasn't starting consistantly, hanging on
systemd-logind. Oddly, it worked well enough to still run build jobs,
but restarting daemons and
