Currently at bundler-1.15.4. Tried both with 2.0.0 from RHEL7 and latest stable Ruby.
[root@nuc foreman]# gem --version 2.0.14.1 [root@nuc foreman]# ruby --version ruby 2.0.0p648 (2015-12-16) [x86_64-linux] [root@nuc bubbles]# gem --version 2.6.13 [root@nuc bubbles]# ruby --version ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux] This is Intel NUC with 8 GB RAM, bundler runs for about a minute before it takes whole memory and start swapping. Then I leave it for another 5 minutes before bringing it down. On Thu, Sep 14, 2017 at 3:36 PM, Ivan Necas <ine...@redhat.com> wrote: > The easiest way to get the recent Gemfile.lock is to look at the build > artifacts in jenkins jobs > (also useful when investigating sudden test failures): > > http://ci.theforeman.org/job/test_develop/database=postgresql,ruby=2.4,slave=fast/ > > -- Ivan > > On Thu, Sep 14, 2017 at 3:34 PM, Ivan Necas <ine...@redhat.com> wrote: >> What errors are you seeing. I've tried with ruby 2.2.2, and 2.3.1 >> bundler 1.15.4, everything worked fine. >> What gem --version do you have? >> >> Anything in `bundler.d/Gemfile.local.rb` that could be causing this? >> >> -- Ivan >> >> On Thu, Sep 14, 2017 at 3:13 PM, Lukas Zapletal <l...@redhat.com> wrote: >>> Hey, >>> >>> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and >>> 2.4.1), bundle install is not able to resolve dependencies and loops >>> forever. I am using latest stable bundler, tried also pre1 version. >>> >>> Can someone confirm and provide a workaround? I think copying >>> Gemfile.lock from someone else should do it. Can someone attach a >>> pastebin me one? I currently have my workstation down (CPU in RMA) and >>> got clean setup. >>> >>> If this is confirmed, it is quite an issue for newcomers. The second >>> command new developer is asked to execute fails hard. Any suggestions? >>> >>> LZ >>> >>> -- >>> Later, >>> Lukas @lzap Zapletal >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to foreman-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
