<
headius>
false positive
<
headius>
I had something failing that was preventing RubyGems from loading
<
headius>
RG alone is still a good 0.4s of startup
<
lopex>
it's parse or exec ?
<
headius>
bit of both
<
headius>
post-parse is most of it though I believe
<
headius>
IR compilation, interp
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
_whitelogger has joined #jruby
_whitelogger has joined #jruby
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<
headius>
kares: hey I saw some countdown latch test fail randomly yesterday
<
headius>
looked like you were fiddling with it so I thought you might want to know
<
headius>
kares: I modified all but one ext load to use load_ext
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
shellac has joined #jruby
drbobbeaty has joined #jruby
lucasb has joined #jruby
_whitelogger has joined #jruby
rdubya has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
<
headius>
kares: any idea why some of these exts would fail to load?
<
headius>
e.g. that build above
shellac has joined #jruby
Nikolay_ has joined #jruby
shellac has quit [Ping timeout: 240 seconds]
xardion has quit [Remote host closed the connection]
xardion has joined #jruby
<
headius>
enebo, kares: no_builtins PR could be reviewed any time
<
headius>
enebo: do you remember how to reproduce the bootsnap issues?
<
headius>
oh maybe it's in the issue
<
enebo>
headius: yeah I think it is in there
<
headius>
looks like just any 5.2 raiks -S server
<
enebo>
hmm although they may have removed it at some point release for jruby when making an app
<
enebo>
it may just be as simple as adding it to gemfile?
<
enebo>
or using an earlier point
<
headius>
yeah they seem to have removed it
<
headius>
5.2.2 does not have bootsnap issues
Nikolay_ has quit [Ping timeout: 256 seconds]
<
headius>
enebo: I haz repro
<
enebo>
./config/boot.rb:require 'bootsnap/setup' # Speed up boot time by caching expensive operations.
<
enebo>
so MRI does add it
<
enebo>
gem 'bootsnap', '>= 1.1.0', require: false
<
headius>
ah so they special cased it for us
<
enebo>
although you I am sure figure this out based on that comment
<
headius>
I just rolled back to 5.2.0
<
enebo>
oh well you can use 5.2.2 with those two lines in Gemfile and boot.rb
<
headius>
who do I have to kill to get rid of .ruby-version
<
enebo>
yeah no kidding
<
enebo>
I don't have the version it is requesting so it just complains when I cd
<
headius>
hmm still broken but I'm looking into it
<
headius>
it still thinks the files are not loadable
<
headius>
"cannot load such file -- cgi/escape"
<
headius>
it's literally just a .rb file now
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<
headius>
woot, I think it's working
<
headius>
enebo: why do we get the `listen` error
<
headius>
is there something rails is supposed to exclude on JRuby but it isn't?
<
enebo>
headius: is that 5.2.0?
<
enebo>
headius: I used to see that but I think they do better at excludes
<
enebo>
or something
<
enebo>
I do not see that with latest 5.2.x
<
enebo>
derp: system('echo gem \"listen\" >> Gemfile')
<
enebo>
ok I guess they did not fix this
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<
headius>
enebo: 5.2.0 for sure
<
headius>
maybe they fixed that
<
headius>
ok master and no_builtins should be green again
subbu is now known as subbu|lunch
subbu|lunch is now known as subbu
<
kares>
headius: yes, that set.rb assumption should be correct - for some reason I did not delete the original .rb file
<
kares>
headius: let me know if you're still seeing that count-down latch failure - haven't seen it fail onCI it might still timeout
<
kares>
who knows - the recent mvn failures on CI seem weird enough
<
kares>
(i do not get them on my jruby fork)
lucasb has quit [Quit: Connection closed for inactivity]