11:27 <stewart_> If I have a ruby object I which a thread is running after calling Thread.new I have noticed that after calling tearDown on that ruby object the thread stays running. Is this a bug or is this behaviour intended? I would expect any running threads to die if tearDown is called.

12:33 <brauliobo> chrisseaton: hi! thanks for offering help :)

12:33 <brauliobo> chrisseaton: the gitter chat room is actually private

12:34 <brauliobo> I would like to fix some simple failing spec on jruby+truflle

12:53 <chrisseaton> brauliobo: hello

12:54 <brauliobo> chrisseaton: do you use eclipse for truffle development? i'm quite new to it, but maybe it would be more productive in jruby+truffle compared to the vim that I use today

12:55 <brauliobo> i've tried to setup jruby+truffle on it but could not find a project

12:56 <chrisseaton> we use IntelliJ (free version is fine) - there are notes on the wiki for using Eclipse but it has problems so I wouldn't recommend

12:57 <brauliobo> chrisseaton: ok, will try it

14:18 <GitHub137> [jruby] chrisseaton pushed 1 new commit to master: http://git.io/vZf1j

14:18 <GitHub137> jruby/master fe19bb5 Chris Seaton: [Truffle] Modify total-allocation to use KB.

14:29 <travis-ci> jruby/jruby (master:fe19bb5 by Chris Seaton): The build is still failing. (https://travis-ci.org/jruby/jruby/builds/79001563)

15:08 <projectodd-ci> Yippee, build fixed!

15:08 <projectodd-ci> Project jruby-master-spec-ji build #1978: FIXED in 17 min: https://projectodd.ci.cloudbees.com/job/jruby-master-spec-ji/1978/

15:37 <projectodd-ci> Yippee, build fixed!

15:37 <projectodd-ci> Project jruby-master-test-slow_suites build #1943: FIXED in 34 min: https://projectodd.ci.cloudbees.com/job/jruby-master-test-slow_suites/1943/

18:04 <donV> kares: Hi! you on?