Re: Status update: updating rubygem-cucumber

[Mamoru TASAKA]

Jarek Prokop wrote on 2022/01/17 7:40:
> On 1/14/22 12:40, Mamoru TASAKA wrote:
> > Hello, all:
> >
> > Jarek Prokop wrote on 2022/01/13 2:17:
> > > Hi,
> > >
> > > On 1/12/22 12:34, Vít Ondruch wrote:
> > > > Hi Jarek,
> > > > > https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
> > > >
> > > > Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
> > >
> > > Right, changes are built & tested using the side-tag: f36-build-side-49108
> > >
> > > Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
> >
> > Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 .
> > Thanks (especially to Pavel and Jarek) for paying attention to this.
> > (And sorry for pushing new aruba late.)
> >
> > I am now trying to rebuild several packages. Note that as Jarek has pointed out
> > (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage:
> > several rpms fails to build with cucumber 7 due to this change and need fixing,
> > e.g.
> > https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
>
> Thanks!
>
> I will start rebuilding the cucumber dependencies with the features tests enabled.

Currently, 2 packages are seeing trouble. But I think now f36-build-side-49108 sidetag can be
merged into f36 main buildroot.

1. rubygem-nifti
Executing rspec and cucumber test suites causes test failure on s390x only (note that srpm
itself is noarch), very likely big endian related, so rebuilding rubygem-nifti causes build failure
if build happens on s390x arch:

https://koji.fedoraproject.org/koji/taskinfo?taskID=81341629

2. rubygem-cucumber-rails
This seems difficult for me... cucumber testsuite fails (even if I relax gemspec dependency) in the way
seemingly difficult.

cucumber testsuite seems to be failing basically by the following code:
```
$ ruby -e "require 'aruba/cucumber'"
/usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber/hooks.rb:4:in `<top (required)>': undefined method `World' for main:Object (NoMethodError)
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require'
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require'
    from /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber.rb:4:in `<top (required)>'
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:160:in `require'
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:160:in `rescue in require'
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:149:in `require'
    from -e:1:in `<main>'
internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- aruba/cucumber (LoadError)
    from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require'
    from -e:1:in `<main>'
```
Looks like some initialization is needed before "require 'aruba/cucumber'", however currently
I have no idea. Maybe updating to the latest cucumber-rails fixes cucumber test, I hope
someone would investigate this further.

Again thanks for work on cucumber update.

Regards,
Mamoru