test failure #58

Closed
wwood opened this Issue Aug 6, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@wwood

wwood commented Aug 6, 2016

Hi there,

I'm trying to get a cucumber package together for GNU Guix. Running the tests which come as part of the 2.4.0 gem after gem unpack gave one failure. Is this expected?

ben@u /tmp/cu/cucumber/psb1blr29rlnsbac8qw7i14lrpq9fyb9-cucumber-2.4.0 [env]# rake spec
fatal: Not a git repository (or any parent up to mount point /tmp/cu/cucumber/psb1blr29rlnsbac8qw7i14lrpq9fyb9-cucumber-2.4.0)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /tmp/cu/cucumber/psb1blr29rlnsbac8qw7i14lrpq9fyb9-cucumber-2.4.0)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /tmp/cu/cucumber/psb1blr29rlnsbac8qw7i14lrpq9fyb9-cucumber-2.4.0)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
/gnu/store/dlagr9ndsgip487j446m8a9hlpd1hbiq-ruby-2.3.1/bin/ruby -I/gnu/store/xg7i10rh7la1xszbr0dx7cgdns78i6c7-profile/lib/ruby/gems/2.3.0/gems/rspec-support-3.5.0/lib:/gnu/store/xg7i10rh7la1xszbr0dx7cgdns78i6c7-profile/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.1/lib /gnu/store/xg7i10rh7la1xszbr0dx7cgdns78i6c7-profile/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.1/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/gnu/store/xg7i10rh7la1xszbr0dx7cgdns78i6c7-profile/lib/ruby/gems/2.3.0/gems/gherkin3-3.1.1/lib/gherkin3/dialect.rb:4: warning: already initialized constant Gherkin3::DIALECT_FILE_PATH
/gnu/store/h5077m4liqsnb8h97pm2mcw208z8jqrq-ruby-gherkin3-3.1.1/lib/ruby/gems/2.3.0/gems/gherkin3-3.1.1/lib/gherkin3/dialect.rb:4: warning: previous definition of DIALECT_FILE_PATH was here
/gnu/store/xg7i10rh7la1xszbr0dx7cgdns78i6c7-profile/lib/ruby/gems/2.3.0/gems/gherkin3-3.1.1/lib/gherkin3/dialect.rb:5: warning: already initialized constant Gherkin3::DIALECTS
/gnu/store/h5077m4liqsnb8h97pm2mcw208z8jqrq-ruby-gherkin3-3.1.1/lib/ruby/gems/2.3.0/gems/gherkin3-3.1.1/lib/gherkin3/dialect.rb:5: warning: previous definition of DIALECTS was here
................................................................................................................................................................................................F.................................................................................................................................................................................................................................................................................................................................................................................................

Failures:

  1) Cucumber::Formatter::Html when writing the report to a file with a step that embeds a snapshot converts the snapshot path to a relative path
     Failure/Error: expect(@out).to receive(:respond_to?).with(:path).and_return(true)

       (#<StringIO:0x005572e56e9d00>).respond_to?(:path)
           expected: 1 time with arguments: (:path)
           received: 3 times with arguments: (:path)
     # ./spec/cucumber/formatter/html_spec.rb:35:in `block (3 levels) in <module:Formatter>'

Finished in 1.59 seconds (files took 0.55264 seconds to load)
578 examples, 1 failure

Your Environment

I'm in a Guix environment with Ruby 2.3.1p112.

ben@u /tmp/cu/cucumber/psb1blr29rlnsbac8qw7i14lrpq9fyb9-cucumber-2.4.0 [env]# gem list 

*** LOCAL GEMS ***

aruba (0.14.1)
bigdecimal (1.2.8)
builder (3.2.2)
bundler (1.12.5)
childprocess (0.5.8)
coderay (1.1.0)
contracts (0.12.0)
cucumber (2.4.0)
cucumber-core (1.5.0)
cucumber-wire (0.0.1)
did_you_mean (1.0.0)
diff-lcs (1.2.5)
event-bus (0.2.1)
ffi (1.9.14)
gherkin (4.0.0)
gherkin3 (3.1.1)
io-console (0.4.5)
json (1.8.3)
method_source (0.8.2)
mini_portile2 (2.1.0)
minitest (5.8.3)
multi_json (1.11.2)
multi_test (0.1.2)
net-telnet (0.1.1)
nokogiri (1.6.8)
pkg-config (1.1.7)
power_assert (0.2.6)
pry (0.10.1)
psych (2.0.17)
rake (10.4.2)
rdoc (4.2.1)
rspec (3.5.0)
rspec-core (3.5.1)
rspec-expectations (3.5.0)
rspec-mocks (3.5.0)
rspec-support (3.5.0)
slop (3.6.0)
test-unit (3.1.5)
thor (0.19.1)

I do not have the git checkout of v1.x-bugfix branch of http://github.com/cucumber/cucumber-ruby-core.git as specified in the Gemfile, but it doesn't seem on first glance to be related to the bug cucumber/cucumber-ruby-core#109

Thanks in advance. ben.

@brasmusson

This comment has been minimized.

Show comment
Hide comment
@brasmusson

brasmusson Aug 6, 2016

Contributor

Is this expected?

No, as you can see on Travis all test for v2.4.0 passes.

You have gherkin3-3.1.1 in the backtrace, v2.4.0 does not use gherkin3 v3.1.1, but gherkin v4.0 as the gemspec specifies.

Contributor

brasmusson commented Aug 6, 2016

Is this expected?

No, as you can see on Travis all test for v2.4.0 passes.

You have gherkin3-3.1.1 in the backtrace, v2.4.0 does not use gherkin3 v3.1.1, but gherkin v4.0 as the gemspec specifies.

@wwood

This comment has been minimized.

Show comment
Hide comment
@wwood

wwood Aug 6, 2016

Is this expected?

No, as you can see on Travis all test for v2.4.0 passes.

OK, good. I did not mean to imply anything negative about this project, apologies if that is what happened.

You have gherkin3-3.1.1 in the backtrace, v2.4.0 does not use gherkin3 v3.1.1, but gherkin v4.0 as the gemspec specifies.

I'm afraid this isn't the issue because v4 is also there. Thanks for this pickup though, it showed an error in a separate package definition. Fixing that error meant that v3 no longer appears in the gem list, but the error still happens minus the Gherkin3 warnings in the backtrace.

I'll keep looking, thanks.

wwood commented Aug 6, 2016

Is this expected?

No, as you can see on Travis all test for v2.4.0 passes.

OK, good. I did not mean to imply anything negative about this project, apologies if that is what happened.

You have gherkin3-3.1.1 in the backtrace, v2.4.0 does not use gherkin3 v3.1.1, but gherkin v4.0 as the gemspec specifies.

I'm afraid this isn't the issue because v4 is also there. Thanks for this pickup though, it showed an error in a separate package definition. Fixing that error meant that v3 no longer appears in the gem list, but the error still happens minus the Gherkin3 warnings in the backtrace.

I'll keep looking, thanks.

@wwood wwood closed this Aug 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment