<fidothe>
Hey all. I was just resuming work on a JRuby based project and ran the tests against 9.2.10.0 by mistake. I got the errors I saw in https://github.com/jruby/jruby/issues/5885, which was fixed in 9.2.9.0 again. Updated to 9.2.11.1 and all was good. Is it worth me writing a simple test case and adding it because this is a nasty regression... (I searched the issues and no one reported it again)
<fidothe>
I've actually been writing Java for money recently, so I feel a little more qualified to tackle this than I did when I started tackling #5952
<venkatkms[m]>
Let me know if you need anything else.
<venkatkms[m]>
Sorry I wish I could do more at my end.
subbu is now known as subbu|lunch
subbu|lunch is now known as subbu
<headius[m]>
Than you for the update
<headius[m]>
woah so many ar-jdbc releases
<fidothe>
@headius[m] I'm seeing the #5885 issue again in 9.2.11.1, which I thought I wasn't earlier. Is it possible that switching JRuby using chruby is leaving some stuff cached that could be affecting this?
<headius[m]>
fidothe there's always room for more tests!
<fidothe>
i think that `chruby jruby` was not doing what I thought it was (switching to latest semver release), but is switching to alpha-sort-last release
<fidothe>
so this is a regression that appeared in 9.2.10
<headius[m]>
huh
<fidothe>
I will write a test tomorrow
<headius[m]>
hah ok you confirmed it was fixed but we never did anything
<headius[m]>
yeah get a test together so we can be sure and fix shouldn't be difficult
<fidothe>
@headius[m] yeah it was fixed in 9.2.9
<fidothe>
at least, it doesn't work in 9.2.8
<fidothe>
and does in 9.2.9
<headius[m]>
ok
<headius[m]>
I will be curious to see if it's fixed on master where we have more module/reflection tweaking
subbu is now known as subbu|bridge
<headius[m]>
blast, of course this doesn't hang on a local linux