-
Notifications
You must be signed in to change notification settings - Fork 202
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
RSpec 3.0.0 breaks rspec-puppet #200
Milestone
Comments
treydock
added a commit
to treydock/rspec-puppet
that referenced
this issue
Jun 2, 2014
stepanstipl
added a commit
to stepanstipl/puppet-inifile
that referenced
this issue
Jun 2, 2014
Duplicate of #198 |
treydock
added a commit
to treydock/rspec-puppet
that referenced
this issue
Jun 2, 2014
* Fix deprecation warnings related to 'display_name', fixes rodjek#198
Closed
javiplx
pushed a commit
to javiplx/rspec-puppet
that referenced
this issue
Aug 4, 2014
* Fix deprecation warnings related to 'display_name', fixes rodjek#198
javiplx
pushed a commit
to javiplx/rspec-puppet
that referenced
this issue
Aug 4, 2014
* Fix deprecation warnings related to 'display_name', fixes rodjek#198
arusso
pushed a commit
to ucbpi/puppet-apache
that referenced
this issue
Sep 19, 2014
gerhardsam
added a commit
to gerhardsam/puppet-rpmbuild
that referenced
this issue
Feb 25, 2015
gerhardsam
added a commit
to gerhardsam/puppet-rpmbuild
that referenced
this issue
Feb 25, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RSpec 3.0.0 was released yesterday and it breaks rspec-puppet.
I enabled backtrace and pushed my puppet module to run in Travis-CI , here is one of the failed tests, https://travis-ci.org/treydock/puppet-osg/jobs/26588391.
For now rspec-puppet should probably require rspec <3.0.0.
Here is one error's backtraces:
With
--deprecation-out .rspec.errors
I get the following entriesThe text was updated successfully, but these errors were encountered: