Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"should have mask_native defined" test failure #1

Open
Apteryks opened this issue Mar 9, 2023 · 0 comments
Open

"should have mask_native defined" test failure #1

Apteryks opened this issue Mar 9, 2023 · 0 comments

Comments

@Apteryks
Copy link

Apteryks commented Mar 9, 2023

Hi,

Running the test suite of the 1.0.0. release, I see:

starting phase `check'
/gnu/store/j4z07lyi1ykk8bc68h1p4bpj1il9dn3f-ruby-2.7.4/bin/ruby -I/gnu/store/900s3ljm1d44zam9hsbxf7ckr49zrriv-ruby-rspec-support-3.12.0/lib/ruby/vendor_ruby/gems/rspec-support-3.12.0/lib:/gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/lib /gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/exe/rspec --pattern spec/\*\*/\*_spec.rb -c -f progress
F..

Failures:

  1) WebSocket::Frame::Data should have mask_native defined
     Failure/Error: subject.respond_to?(:mask_native).should be_true
       expected true to respond to `true?` or perhaps you meant `be true` or `be_truthy`
     # ./spec/websocket_spec.rb:8:in `block (2 levels) in <top (required)>'

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /tmp/guix-build-ruby-websocket-native-1.0.0.drv-0/gem/spec/websocket_spec.rb:8:in `block (2 levels) in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 0.00936 seconds (files took 0.0532 seconds to load)
3 examples, 1 failure

Failed examples:

rspec ./spec/websocket_spec.rb:7 # WebSocket::Frame::Data should have mask_native defined

/gnu/store/j4z07lyi1ykk8bc68h1p4bpj1il9dn3f-ruby-2.7.4/bin/ruby -I/gnu/store/900s3ljm1d44zam9hsbxf7ckr49zrriv-ruby-rspec-support-3.12.0/lib/ruby/vendor_ruby/gems/rspec-support-3.12.0/lib:/gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/lib /gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/exe/rspec --pattern spec/\*\*/\*_spec.rb -c -f progress failed
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "rake" arguments: ("spec") exit-status: 1 term-signal: #f stop-signal: #f> 
phase `check' failed after 0.2 seconds
command "rake" "spec" failed with status 1

I've skipped that test for now (packaging for GNU Guix).

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant