gistfile1.txt

# rake spec_standalone 


Deprecation Warnings:

Filtering by an `:example_group` subhash is deprecated. Use the subhash to filter directly instead. Called from /var/lib/gems/1.9.1/gems/rspec-puppet-1.0.1/lib/rspec-puppet/example.rb:12:in `block in <top (required)>'.
Filtering by an `:example_group` subhash is deprecated. Use the subhash to filter directly instead. Called from /var/lib/gems/1.9.1/gems/rspec-puppet-1.0.1/lib/rspec-puppet/example.rb:16:in `block in <top (required)>'.
Filtering by an `:example_group` subhash is deprecated. Use the subhash to filter directly instead. Called from /var/lib/gems/1.9.1/gems/rspec-puppet-1.0.1/lib/rspec-puppet/example.rb:20:in `block in <top (required)>'.
Too many uses of deprecated 'Filtering by an `:example_group` subhash'. Pass `--deprecation-out` or set `config.deprecation_stream` to a file for full output.

--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CountGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:19:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CountGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:25:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CountGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:69:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
Too many similar deprecation messages reported, disregarding further reports. Pass `--deprecation-out` or set `config.deprecation_stream` to a file for full output.

--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:23:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:32:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
RSpec::Puppet::ManifestMatchers::CreateGeneric implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /etc/puppet/modules/axcloud/spec/defines/axcloud_mount_dir_spec.rb:73:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------------
Too many similar deprecation messages reported, disregarding further reports. Pass `--deprecation-out` or set `config.deprecation_stream` to a file for full output.


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.

12 deprecation warnings total

Finished in 0.52057 seconds (files took 0.75597 seconds to load)
11 examples, 0 failures
Run options: 

# Running tests:



Finished tests in 0.001399s, 0.0000 tests/s, 0.0000 assertions/s.

0 tests, 0 assertions, 0 failures, 0 errors, 0 skips