<kares[m]>
<headius> "kares: I can review your error-..." <- Should be done but somehow never got green on my fork, but things pass locally - not sure what's going on with CI. should be back next week I can give it another try...
razetime has quit [Ping timeout: 260 seconds]
razetime has joined #jruby
subbu has joined #jruby
joast has quit [Quit: Leaving.]
nilsding has quit [Remote host closed the connection]
subbu has quit [Ping timeout: 245 seconds]
subbu has joined #jruby
razetime has quit [Ping timeout: 245 seconds]
<headius>
kares: I'll have a peek
<headius>
enebo: yesterday was spent getting jruby-maven-plugins moved to jruby org, org.jruby.maven group ID, and getting all the tests green again
<headius>
that and mavengem are now green and should be possible to deploy, though there's some circular relationships I haven't sorted out yet
<headius>
then I ran into an issue where the polyglot subsystem also hardcodes de.saumya.mojo group ID for some stuff, but I have a workaround for now (we'll need to take over maven-tools too at some point to fix this)
<headius>
ok so I need releases of maven-tools gem and polyglot-ruby to propagate the group ID change
<headius>
quagmire
subbu has quit [Ping timeout: 260 seconds]
<kalenp[m]>
alright, I finally got around to getting a heap dump of an OOM process from a CI run (set a lower memory limit and ran it locally)
<kalenp[m]>
at the top of the stats is 6M Blocks, taking up 248MB. is there a way to tell where those blocks are allocated from? exploring around their structures and not finding something obvious like line number and file