Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 356269 - Stabilize dev-ruby/rspec-1.3.1 and dependencies
Summary: Stabilize dev-ruby/rspec-1.3.1 and dependencies
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on: 353130 354481 354609 355299
Blocks: 333867 352483 358723 364215 368723
  Show dependency tree
 
Reported: 2011-02-24 06:52 UTC by Hans de Graaff
Modified: 2011-07-22 13:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans de Graaff gentoo-dev Security 2011-02-24 06:52:14 UTC
I'd like to request the stabilization of dev-ruby/rspec-1.3.1 and its dependencies. RSpec is used by many packages to run tests, so stabilizing this package is blocking for quite a few ruby packages that use the ruby-ng framework. This stabilization is also blocking for the forthcoming rails stabilization, so I have added all arches that have rails stable.

=dev-ruby/heckle-1.4.3-r2
=dev-ruby/fakefs-0.2.1
=dev-ruby/syntax-1.0.0-r2
=dev-ruby/rspec-1.3.0
Comment 1 Hans de Graaff gentoo-dev Security 2011-02-24 06:53:10 UTC
Aargh. And I mess up the rspec version. Corrected list:

=dev-ruby/heckle-1.4.3-r2
=dev-ruby/fakefs-0.2.1
=dev-ruby/syntax-1.0.0-r2
=dev-ruby/rspec-1.3.1
Comment 2 Markos Chandras (RETIRED) gentoo-dev 2011-02-27 21:56:39 UTC
amd64 done
Comment 3 Thomas Kahle (RETIRED) gentoo-dev 2011-03-08 09:55:48 UTC
x86 done. Thanks!
Comment 4 Brent Baude (RETIRED) gentoo-dev 2011-03-27 19:26:56 UTC
ppc done
Comment 5 Michael Weber (RETIRED) gentoo-dev 2011-04-01 08:05:31 UTC
sparc done
Comment 6 Raúl Porcel (RETIRED) gentoo-dev 2011-04-16 17:27:41 UTC
ia64 stable
Comment 7 Mark Loeser (RETIRED) gentoo-dev 2011-07-10 23:24:39 UTC
Ran into 2 test failures for this (on ppc64):


mock failure should tell you when it receives the right message with the wrong args if you stub the method (fix bug 15719)
./spec/spec/mocks/bug_report_15719_spec.rb:16

1)
Spec::Mocks::MockExpectationError in 'ExampleGroupMethods#run_before_all does not create an instance if before_all_parts are empty'
<#<Class:0xfff93f76cd0> (class)> expected :new with (before(:all)) 0 times, but received it once
./spec/spec/example/example_group_methods_spec.rb:662:in `__send__'
./spec/spec/example/example_group_methods_spec.rb:662:
/usr/lib64/ruby/1.8/timeout.rb:67:in `timeout'

2)
NoMethodError in 'ExampleGroupMethods#run_after_all does not create an instance if after_all_parts are empty'
undefined method `reporter' for nil:NilClass
./spec/spec/example/example_group_methods_spec.rb:670:in `__send__'
./spec/spec/example/example_group_methods_spec.rb:670:
/usr/lib64/ruby/1.8/timeout.rb:67:in `timeout'
Comment 8 Hans de Graaff gentoo-dev Security 2011-07-11 18:24:13 UTC
(In reply to comment #7)

> mock failure should tell you when it receives the right message with the wrong
> args if you stub the method (fix bug 15719)
> ./spec/spec/mocks/bug_report_15719_spec.rb:16

This is a pending spec that can safely be ignored.

> 1)
> Spec::Mocks::MockExpectationError in 'ExampleGroupMethods#run_before_all does
> not create an instance if before_all_parts are empty'
> <#<Class:0xfff93f76cd0> (class)> expected :new with (before(:all)) 0 times, but
> received it once
> ./spec/spec/example/example_group_methods_spec.rb:662:in `__send__'
> ./spec/spec/example/example_group_methods_spec.rb:662:
> /usr/lib64/ruby/1.8/timeout.rb:67:in `timeout'
> 
> 2)
> NoMethodError in 'ExampleGroupMethods#run_after_all does not create an instance
> if after_all_parts are empty'
> undefined method `reporter' for nil:NilClass
> ./spec/spec/example/example_group_methods_spec.rb:670:in `__send__'
> ./spec/spec/example/example_group_methods_spec.rb:670:
> /usr/lib64/ruby/1.8/timeout.rb:67:in `timeout'

I can't explain these. It looks like the setup for these specs has issues which causes errors or which at least causes the wrong path to be taken in the code. Hard to debug from a distance. I'm not sure if this version is still supported by upstream.

Long shot debugging attempt: do you perhaps have an old version of rspec installted (either through portage or as a gem)?
Comment 9 Mark Loeser (RETIRED) gentoo-dev 2011-07-17 17:41:29 UTC
(In reply to comment #8)
> I can't explain these. It looks like the setup for these specs has issues which
> causes errors or which at least causes the wrong path to be taken in the code.
> Hard to debug from a distance. I'm not sure if this version is still supported
> by upstream.
> 
> Long shot debugging attempt: do you perhaps have an old version of rspec
> installted (either through portage or as a gem)?

This is a completely new install, and the only time I've ever tried to install rspec.
Comment 10 Hans de Graaff gentoo-dev Security 2011-07-18 07:42:40 UTC
I've just added 1.3.2 to the tree which has some bug fixes. Could you try that version to see if that works?
Comment 11 Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev 2011-07-22 13:04:06 UTC
cannot reproduce those failures on my 2 boxes, so I guess we'll proceed.

rspec has some missing dependencies for USE="test"

Running test phase for ruby18 ...
(in /var/tmp/portage/dev-ruby/rspec-1.3.1/work/ruby18/rspec-1.3.1)
which: no dot in (/usr/lib64/portage/bin/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/powerpc64-unknown-linux-gnu/gcc-bin/4.4.5)
You need cucumber installed to run cucumber tasks
nokogiri not loaded -- skipping TextMateFormatter specs
nokogiri not loaded -- skipping HtmlFormatter specs

so I guess:
media-gfx/graphviz
dev-util/cucumber
dev-ruby/nokogiri

Nevertheless, ppc64 stable, last arch done