#7 Fail to install fruit_processor_gem on CentOS 6 (VM)
Running rake install in the fruit_processor_gem directory, after replacing two relevant test files by their ruby2 version, I get an error on the execution of the ruby misc_test.rb part, at MiscTest#test_os_install. I can't share the clipboard between VM and Windows, so I'll copy a simplified error report below. Excution with sudo or as su made no difference.
run misc_text.rb
Run options: --seed 15023Running:
E
Finished in 0.004122s, 242.6248 runs/s, 0.0000 assertions/s.
1) Error:
MiscTest#test_os_install:
Errno::EROFS: Read-only file system @ rb_file_s_symlink - (os_install_from.txt, os_install_to.txt)
/opt/rbenv/versions/2.5.3/lib/ruby/2.5.0/fileutils.rb:323:in 'simlink'
/opt/.../fileutils.rb:323:in 'block in ln_s'
/opt/.../fileutils.rb:1479:in 'fu_each_src_dest0'
/opt/.../fileutils.rb:321: in 'ln_s'
/opt/.../fileutils.rb:240: in 'ln_sf'
.../fruit_processor_gem/lib/misc.rb:63:in 'os_install'
misc_test.rb:19: in 'test_os_install'
1 runs, 0 assertions, 0 failures, 1 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby misc_test.rb...]
.../fruit_processor_gem/rakefile:80:in 'block (2 levels) in <top (required)="">'
.../fruit_processor_gem/rakefile:78:in 'chdir'
.../fruit_processor_gem/rakefile:78:in 'block in <top (required)="">'
Tasks: TOP => install => default => test</top></top>
Thanks for the report. I'll try to reproduce and fix it in the coming weekend.
I've tried to reproduce the problem on a newly installed CentOS 6 (VM), ruby 2.4.5p335, and fruit_3.4.3. "ruby misc_test.rb" did not cause error as shown below. Cassio, more information highly appreciated. Could you inform us version of rake and which command generated the error log?
Running "ruby misc_test.rb" using ruby 2.5.3 through rbenv was also successful. So, I haven't been able to reporduce the problem [#7 Fail to install fruit_processor_gem on CentOS 6 (VM) ].
Ok, I guess I got it.
I'm using Devtoolset-7 and rbenv 2.5.3, also in CentOS 6.10. Since you couldn't reproduce the error, I tried some extra investigation locally, assuming FRUIT basic inner workings are fine. I think I understood the problem.
I had fruit directory in a folder shared between the VM (VirtualBox) and the host, which requires that the user belongs to a specific group (vboxsf, vboxusers) to be able to access this folder. It seems to be related to that. Naturally, my user (as well as su) belongs to this group, but I suppose some issue happens when invoking subprocesses.
Anyway, I copied the FRUIT files to a folder outside of the shared one, and it worked fine. You may try to check it if you are curious, or just close the ticket, as you see fit.
And thanky you for the speedy response, it was greatly appreciated! =)