14:28 <headius[m]> Good morning!

15:22 <lopex> numbers!

16:26 <headius[m]> yeesh, finally caught up expenses for the last 6 months

16:26 <headius[m]> I need personal assistant

19:08 <travis-ci> jruby/jruby (master:441e5d1 by Thomas E. Enebo): The build was broken. https://travis-ci.org/jruby/jruby/builds/643518076 [182 min 17 sec]

19:18 <travis-ci> jruby/jruby (master:441e5d1 by Thomas E. Enebo): The build was canceled. https://travis-ci.org/jruby/jruby/builds/643518076 [182 min 20 sec]

19:19 <enebo[m]> headius: did you cancel that?

19:19 <enebo[m]> I guess the next job shold run but I just restarted the fail and it has just finished green within about 2s of that cancel

19:20 <enebo[m]> in any case that must be a flaky test in ruby-concurrent

19:51 <headius[m]> I did not

19:51 <headius[m]> it says that when you restart a failed job and it passes because the snapshot deploy build remains cancelled

19:51 <headius[m]> it's dumb

19:51 <enebo[m]> wot

19:51 <headius[m]> the snapshot deploy is predicated on the other builds passing

19:52 <enebo[m]> ok and I only thought it could be you...no official blame was cast :P

19:52 <enebo[m]> that is pretty weird

19:52 <enebo[m]> why would that be useful

21:15 <headius[m]> enebo: maybe it's useful to let you know that there were jobs that didn't run but this is a very confusing way to do it

21:15 <headius[m]> cancelled makes it sound like someone actively cancelled it, when it was just not run