Alexandr Evstigneev
Alexandr Evstigneev
Here are docker images we are running our tests in: ``` docker pull rubymine/test_environment:rvm-single-ssh-jruby-92 docker pull rubymine/test_environment:rvm-single-ssh-jruby-91 docker pull rubymine/test_environment:rbenv-ssh-user ``` Currently we have only last versions. There are also...
Regarding the concurrency, I was thinking more about some jruby internal parallelization, unrelated to specific gems or code. Haven't looked at jruby code yet.
Jruby 9.3.0 update: Looks like problem with constant resolve is gone (so far at least). Still `Nil` appeared few times in unexpected places. Like: ``` $ bash -c "/home/user/.rvm/bin/rvm jruby-9.3.0.0...
The problem that it happens on CI, i don't remember local reproduction (never tried intentionally, honestly) I'll check if it's possible to add `-X.log.exceptions` to jruby - related tests. Meanwhile:...
Added debugging options to our CI few days ago. So far - no failures :D Let's wait.
Got a gem install failure with log and debug options: ``` $ bash -c ". /usr/local/share/chruby/chruby.sh && chruby jruby-9.3.2.0 && /home/user/.rubies/jruby-9.3.2.0/bin/jruby -Xlog.exceptions /home/user/.rubies/jruby-9.3.2.0/bin/jgem install pry --version '= 0.13.1' --no-document --backtrace...
updated rubygems on CI to 3.3.5 go get this update. Will see if it helps.
@MSP-Greg i disagree. We have no compilation error or missing library error. We have a pacman locked error. This means: 1. `openssl` installation failed and was not properly reported by...
@MSP-Greg oh, thank you for the clarification. May be I should address this issue to the rubyinstaller2 then. I believe it's up to date. We have all rubies 2.4+ installed...