Created attachment 895873 [details]
Description of problem:
Errno::EINVAL: Invalid argument @ rb_io_seek - /tmp/test_io20140515-16559-1kttlg6
/builddir/build/BUILD/ruby-2.1.1/test/ruby/test_io.rb:1696:in `block (2 levels) in test_seek'
/builddir/build/BUILD/ruby-2.1.1/test/ruby/test_io.rb:1694:in `block in test_seek'
Errno::EINVAL: Invalid argument @ rb_io_seek - /tmp/test_io20140515-16559-yjley0
/builddir/build/BUILD/ruby-2.1.1/test/ruby/test_io.rb:1732:in `block (2 levels) in test_seek_symwhence'
/builddir/build/BUILD/ruby-2.1.1/test/ruby/test_io.rb:1730:in `block in test_seek_symwhence'
15005 tests, 2457850 assertions, 0 failures, 2 errors, 31 skips
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Steps to Reproduce:
1: ppc-koji build --scratch f21 ruby-2.1.1-19.fc21.src.rpm
I think this is a known problem when you run the build on old kernel. There are new SEEK_* options in headers (found by configure and used in build), but they are not supported by the old kernel.
Created attachment 895977 [details]
patch to check if the kernel supports SEEK_DATA/SEEK_HOLE
taken from http://mla.n-z.jp/~w3ml/w3ml.cgi/ruby-changes/msg/33585 and
Tests succeeded on ppc and ppc64, but fail on the primary archs for an unrelated reason
hmm, close but not quite there yet. PPC failed later on with a statfs error.
Created attachment 896528 [details]
revised lseek patch
Scratch builds with this patch succeeded on PPC (RHEL-6 koji builder with kernel 2.6.32) and on primary archs with a much newer 3.x Fedora kernel.
Thanks for the patch. However, I hesitate to apply this patch and carry it in Fedora forever. Would you mind to propose this patch to Ruby upstream or should I?
as this is a stripped down version of the upstream patch, I'd expect that this patch becomes obsolete with the next ruby release. So there's no need to bounce that back to upstream, they are aware of the issue and fixed it already in ruby-trunk
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.