On Sat, Jun 03, 2017 at 03:23:35PM -0700, Vagrant Cascadian wrote:
> Hrm. Several hours later, jtx1a and ff64a still appear to be idle,
> according to munin. *sigh*
thanks for checking…! (I also wondered why 14 jobs where shown as down
in the performance page but was busy doing some last minute
On 2017-06-03, Holger Levsen wrote:
> On Sat, Jun 03, 2017 at 09:27:38AM -0700, Vagrant Cascadian wrote:
>> On a related note, I haven't noticed any builds on ff64a or jtx1a... did
>> all their partner machines happen to be marked as disabled?
>
> there was a problem with the (new) build service
On Sat, Jun 03, 2017 at 09:27:38AM -0700, Vagrant Cascadian wrote:
> > what's your plan for this machine now? I've currently disabled it's build
> > jobs.
> Keep troubleshooting it... push the issue upstream and/or put it on the
> back burner... haven't found anything really informative yet.
ok,
On Fri, Jun 02, 2017 at 08:46:14AM -0700, Vagrant Cascadian wrote:
> > < h01ger> | ff64a seems quite slow
> Yes, disk i/o seems likely, although shouldn't be hugely worse than any
> of the other systems...
I'm not so sure of this but let's see what stats we'll have in a week or so…
>
