shortCircuit__ has quit [Ping timeout: 260 seconds]
shortCircuit__ has joined #jruby
rdubya1 has joined #jruby
rdubya has quit [Ping timeout: 246 seconds]
shortCircuit__ has quit [Ping timeout: 250 seconds]
shortCircuit__ has joined #jruby
shortCircuit__ has quit [Ping timeout: 260 seconds]
shortCircuit__ has joined #jruby
shortCircuit__ has quit [Ping timeout: 276 seconds]
shortCircuit__ has joined #jruby
shortCircuit__ has quit [Ping timeout: 250 seconds]
shortCircuit__ has joined #jruby
shortCircuit__ has quit [Quit: WeeChat 1.8]
shellac has joined #jruby
Puffball has quit [Remote host closed the connection]
shellac has quit [Quit: Computer has gone to sleep.]
shellac has joined #jruby
shellac has quit [Client Quit]
shellac has joined #jruby
drbobbeaty has quit [Ping timeout: 265 seconds]
sidx64 has joined #jruby
sidx64 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sidx64 has joined #jruby
sidx64 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sidx64 has joined #jruby
sidx64 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
drbobbeaty has joined #jruby
akp has joined #jruby
akp has quit [Client Quit]
xardion has quit [Remote host closed the connection]
xardion has joined #jruby
shellac has quit [Quit: Leaving]
<headius>
yo yo
<headius>
kares: if we can get a release out that at least boots and installs gems, I'll be happy for 9.2. The cert stuff needs to be fixed for sure, but I propose we focus on the rest of JDK 9+ compat after 9.2 is out, for our own sanity
shellac has joined #jruby
Puffball has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
shellac has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
subbu is now known as subbu|lunch
shellac has joined #jruby
<kares>
headius: okay I will take a look but I am not home yet ...
<kares>
hopefully the only problem is the JVM version pasrsing
subbu|lunch is now known as subbu
<kares>
so that we can release - although there might be ssl suite failures, guess we'll see
<kares>
should have a clear picture around the end of this week
<headius>
kares: you don't happen to know why we're failing some Psych date/time-related MRI tests on master, do you?
<headius>
I don't see anything that looks like an obvious cause
<kares>
headius: maybe the date-time rewrite I did
<headius>
did that land in the last week ro so?
<headius>
or
<kares>
nope
<kares>
month+ before
<headius>
I haven't been paying attention to CI but I thought it was green just a few days ago
<headius>
ok
<kares>
yep it was
<headius>
it's something trivial... it's using +0000 instead of UTC or vice versa
<kares>
when it landed it was all green
<kares>
oh yeah I have seen that
<kares>
not sure really as I haven't looked closer
<headius>
yeah weird
<headius>
not terribly critical but I don't know why it suddenly regressed
<GitHub101>
[jruby] headius opened pull request #5170: Clone frame and block before proceeding into class_exec logic. (master...clone_more_block_for_exec) https://git.io/vpQzf
<GitHub31>
[jruby] headius closed pull request #5170: Clone frame and block before proceeding into class_exec logic. (master...clone_more_block_for_exec) https://git.io/vpQzf
<GitHub91>
[jruby] headius closed issue #4962: BUG: binding visibility for class_exec not thread safe? https://git.io/vNm0N
<GitHub50>
jruby/master f26c752 Charles Oliver Nutter: Merge pull request #5170 from jruby/clone_more_block_for_exec...