| Summary: | dev-ruby/rbs-3.4.4 fails tests if rspec-support has broken dependencies | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
| Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | kingjon3377 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dev-ruby:rbs-3.4.4:20240701-005115.log
emerge-info.txt |
||
Created attachment 896684 [details]
emerge-info.txt
I think we'll need to patch out that test. Pulling in rspec as a test dependency for rbs is nog going to work because it would lead to a huge dependency tree for dev-lang/ruby. |
Created attachment 896683 [details] dev-ruby:rbs-3.4.4:20240701-005115.log While doing the Ruby 3.2 update on this machine (along with Python 3.12 and other much-postponed updates), I just hit a test failure in =dev-ruby/rbs-3.4.4. My first thought was that this was a case where the dependency, undeclared by the ebuild, is scheduled to be updated later, but in this build log the failure is actually while running the tests with Ruby 3.1 ... And while the failure message talks about missing rspec-support (which has been updated to version 3.13.1 and for Ruby 3.2), the test-code snippet provided references rspec-mocks (which is at version 3.12.6, and only installed for Ruby 3.1).