https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    do you need that so urgently?
  • p
    Not super urgently, but I'd like to start testing and proving out my puppet "soon"
  • v
    I am hoping that we get vagrant instances in a few days/wesk
  • p
    I can give it a few weeks
  • v
    perfect
  • v
    since Puppet Inc is incredible slow with providing new packages, merging the module update now won't bring much benefits anyways
  • v
    bastelfreak: with the reversal of default formatting in https://github.com/puppetlabs/puppetlabs_spec_helper/pull/454 do we need to do something in our tooling?
  • v
    yes
  • v
    well
  • v
    maybe! :D
  • v
    I'd still like to pull out the fixture preparation to its own gem and then get rid of puppetlabs_spec_helper
  • v
    so we don't run that task in CI. but if someone runs it locally, the output will have a different format
  • v
    yes
  • v
    but this only changes the formatting, it doesn't break our setup nor local testing, so I didn't work on it yet
  • v
    fair enough
  • v
    bastelfreak: yesterday I took some time to work on https://github.com/ekohl/puppet_fixtures and at least wrote the test infra that deals with an empty project; next step is to start with some examples and verify those
  • v
    "No backend type is specified. Fall back to :exec type." why is "rake spec" spamming me with these?
  • v
    ewoud: ah nice!
  • v
    Zhenech: oh I haven't seen that one yet. where?
  • v
    bastelfreak, theforeman/pulpcore
  • d
  • v
    locally with puppet7/ruby27
  • v
    Zhenech: I found those too if some facts are missing
  • v
    not using on_supported_os could lead to some of those errors
  • v
    ewoud, also, sorry for your inbox :)
  • v
    puppet-pulpcore uses on_s_o tho
  • v
    did you update any gems recently?
  • v
    today
  • v
    I've seen it many times in the past
  • v
1...598599600...648Latest