| Summary: | dev-util/cucumber-wire-5.0.1: fails tests (Failure/Error: require 'cucumber/configuration') | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sam James <sam> |
| Component: | Current packages | Assignee: | Hans de Graaff <graaff> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | kingjon3377 |
| Priority: | Normal | Keywords: | TESTFAILURE |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Sam James
2021-10-10 20:52:39 UTC
I see the same issue with cucumber-wire-6.2.1. This file is provided by dev-util/cucumber and that is already a test dependency, so I don't know what is going wrong here based on the build.log alone. I went into the unpacked source after the test failure and added 'puts $:' before the 'require' line identified in the LoadError. (That's what some quick Web searching turned up as the way to find out what directories 'require' is searching through.) When I then reran the ebuild phase, it gave me this output: /var/tmp/portage/dev-util/cucumber-wire-6.2.1/work/ruby27/cucumber-wire-6.2.1/spec /var/tmp/portage/dev-util/cucumber-wire-6.2.1/work/ruby27/cucumber-wire-6.2.1/lib /usr/lib64/ruby/gems/2.7.0/gems/did_you_mean-1.4.0/lib /usr/lib64/ruby/gems/2.7.0/gems/rspec-support-3.10.2/lib /usr/lib64/ruby/gems/2.7.0/gems/rspec-core-3.10.1/lib /usr/lib64/ruby/gems/2.7.0/gems/diff-lcs-1.4.4/lib /usr/lib64/ruby/gems/2.7.0/gems/rspec-expectations-3.10.1/lib /usr/lib64/ruby/gems/2.7.0/gems/rspec-mocks-3.10.2/lib /usr/lib64/ruby/gems/2.7.0/gems/rspec-3.10.0/lib /usr/lib64/ruby/gems/2.7.0/gems/cucumber-cucumber-expressions-14.0.0/lib /usr/lib64/ruby/gems/2.7.0/gems/json-2.5.1/lib /usr/lib64/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/json-2.5.1 /usr/lib64/ruby/gems/2.7.0/gems/cucumber-messages-17.1.1/lib /usr/lib64/ruby/gems/2.7.0/gems/cucumber-gherkin-22.0.0/lib /usr/lib64/ruby/gems/2.7.0/gems/cucumber-tag-expressions-4.1.0/lib /usr/lib64/ruby/gems/2.7.0/gems/cucumber-core-10.1.1/lib /usr/lib64/ruby/site_ruby/2.7.0 /usr/lib64/ruby/site_ruby/2.7.0/x86_64-linux /usr/lib64/ruby/site_ruby /usr/lib64/ruby/vendor_ruby/2.7.0 /usr/lib64/ruby/vendor_ruby/2.7.0/x86_64-linux /usr/lib64/ruby/vendor_ruby /usr/lib64/ruby/2.7.0 /usr/lib64/ruby/2.7.0/x86_64-linux I don't know where or how the $LOAD_PATH gets set, but it looks to me like everything from $RDEPEND is in it but dev-util/cucumber, which is only in $BDEPEND, is not. cucumber-wire is an obsolete component used by older cucumber versions. It is currently masked for removal. |